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 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

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,

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 com