Re: salsa.debian.org: merge requests and such
- To: Jacob Adams <email@example.com>
- Cc: firstname.lastname@example.org
- Subject: Re: salsa.debian.org: merge requests and such
- From: Matthew Vernon <email@example.com>
- Date: Tue, 06 Nov 2018 15:00:03 +0000
- Message-id: <[🔎] firstname.lastname@example.org>
- In-reply-to: <15BFA441-893C-48DF-A87D-E11C05B61B99@gmail.com> (Jacob Adams's message of "Sat, 27 Oct 2018 16:47:25 GMT")
- References: <email@example.com> <firstname.lastname@example.org> <15BFA441-893C-48DF-A87D-E11C05B61B99@gmail.com>
Jacob Adams <email@example.com> writes:
> The consensus seems to be that people should enable email
> notifications in salsa and open a bug when filing a merge request.
Relatedly, what's the etiquette about commits to master? I recently
discovered that someone else had pushed a commit to the tip of master of
one of the packages I maintain (and not notified me); when I complained
I was told that emailing would be too much effort. Am I wrong to feel
that at least a MR is something I should have expected as a package
maintainer, not just commits to master?
[I don't really mean to have a go at the person concerned; I'd just like
to know what to expect in future...]
"At least you know where you are with Microsoft."
"True. I just wish I'd brought a paddle."