Re: Fwd: [Python-modules-commits] [python-mplexporter] 135/135: Merge pull request #30 from rainwoodman/patch-1

2014-09-24 Thread Matthias Urlichs
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

Re: Fwd: [Python-modules-commits] [python-mplexporter] 135/135: Merge pull request #30 from rainwoodman/patch-1

2014-09-24 Thread Julian Taylor
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

Re: Fwd: [Python-modules-commits] [python-mplexporter] 135/135: Merge pull request #30 from rainwoodman/patch-1

2014-09-24 Thread Raphael Hertzog
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

Re: Fwd: [Python-modules-commits] [python-mplexporter] 135/135: Merge pull request #30 from rainwoodman/patch-1

2014-09-24 Thread Sandro Tosi
On Wed, Sep 24, 2014 at 8:14 AM, Julian Taylor jtaylor.deb...@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

Fwd: [Python-modules-commits] [python-mplexporter] 135/135: Merge pull request #30 from rainwoodman/patch-1

2014-09-23 Thread Sandro Tosi
Hi all, there's some people who's subscribed to the commit ml, so getting all the changes done to our repos. Now, with the transition to git we are getting this: 135 emails for updating a package (and these are only upstream changes). Did you consider this side effect? Do you have a plan to reduce

Re: Fwd: [Python-modules-commits] [python-mplexporter] 135/135: Merge pull request #30 from rainwoodman/patch-1

2014-09-23 Thread W. Martin Borgert
On 2014-09-23 22:29, Sandro Tosi wrote: there's some people who's subscribed to the commit ml, so getting all the changes done to our repos. Now, with the transition to git we are getting this: 135 emails for updating a package (and these are only upstream changes). Did you consider this side

Re: Fwd: [Python-modules-commits] [python-mplexporter] 135/135: Merge pull request #30 from rainwoodman/patch-1

2014-09-23 Thread Charles Plessy
Le Tue, Sep 23, 2014 at 10:29:10PM +0100, Sandro Tosi a écrit : Hi all, there's some people who's subscribed to the commit ml, so getting all the changes done to our repos. Now, with the transition to git we are getting this: 135 emails for updating a package (and these are only upstream

Re: Fwd: [Python-modules-commits] [python-mplexporter] 135/135: Merge pull request #30 from rainwoodman/patch-1

2014-09-23 Thread Scott Kitterman
On September 23, 2014 6:46:58 PM EDT, Charles Plessy ple...@debian.org wrote: Le Tue, Sep 23, 2014 at 10:29:10PM +0100, Sandro Tosi a écrit : Hi all, there's some people who's subscribed to the commit ml, so getting all the changes done to our repos. Now, with the transition to git we are