Re: Fwd: [Python-modules-commits] [python-mplexporter] 135/135: Merge pull request #30 from rainwoodman/patch-1
On Wed, Sep 24, 2014 at 8:14 AM, Julian Taylor
<jtaylor.debian@googlemail.com> wrote:
> On 24.09.2014 08:14, Matthias Urlichs wrote:
>> Hi,
>>
>> Scott Kitterman:
>>> This kind of nonsense is a great reason to stay with svn.
>>>
>> Nah. It's a great reason to teach the tool in question to be *way* more
>> reasonable. Who needs a single email per commit? Esp. since the number of
>> actual commits will go way up with increased git usage – feature branches
>> are easy in git, and more granular commits are a great way to help with
>> tracking down exactly which change introduced a regression.
>>
>
> Single mails/irc messages per commmit are very useful, they help a lot
> to find mistakes others are making before an upload happens.
absolutely, this feature should be preserved: one commit one message
for Debian packaging changes.
> What we don't want is messages for upstream changes. This should be
> simple to fix, simply check the changed paths for debian/ before sending
> a message.
and I agree with this too, but since several workflows were proposed,
and IIRC there's one where keeping the patches in branches to be
updated at new upstream release, we should also get the diff emails
for such branches. just maybe skip any changes in upstream/* (or
whatever other name we'll choose) branches? (or only a brief
notification a new push has been made on that branch)
Cheers,
--
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi
Reply to: