Re: Fwd: [Python-modules-commits] [python-mplexporter] 135/135: Merge pull request #30 from rainwoodman/patch-1
Hi,
On Wed, 24 Sep 2014, Julian Taylor wrote:
> > 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.
>
> 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.
The default script in use on Alioth is based on git-multimail:
https://github.com/mhagger/git-multimail
It doesn't have such a path-based filtering. But it's Python \o/
So it would be nice it you could contribute such a feature upstream. :-)
That said using maxCommitEmail is still a good safeguard.
There's also the possibility of only using refchangeList (instead of
mailinList) so that we only send out the summary mail of what has been
pushed. The caveat being that we don't get diff of the changes wich
is what makes those email notifications interesting.
Cheers,
--
Raphaël Hertzog ◈ Debian Developer
Discover the Debian Administrator's Handbook:
→ http://debian-handbook.info/get/
Reply to: