Re: [python-committers] Blocking commits to 2.6

2010-04-25 Thread Nick Coghlan
Georg Brandl wrote: > Hi, > > to make my life easier, I'd like to block all unmerged commits in 2.6 that > nobody will merge anyway. I use ``svnmerge avail --log`` to find out which > commits I have to merge, and with the current number of unmerged commits it > is taking longer and longer. > > D

Re: [python-committers] Blocking commits to 2.6

2010-04-25 Thread Jesus Cea
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 25/04/10 19:59, Barry Warsaw wrote: >> Does anyone else use svnmerge integration info on the 2.6 branch? Please >> speak up, so that I don't mess up your workflow. > > Not me. I find the whole svnmerge stuff madness anyway. :) Mercurial can not

Re: [python-committers] Blocking commits to 2.6

2010-04-25 Thread Barry Warsaw
On Apr 25, 2010, at 1:18 PM, Georg Brandl wrote: > to make my life easier, I'd like to block all unmerged commits in 2.6 that > nobody will merge anyway. I use ``svnmerge avail --log`` to find out which > commits I have to merge, and with the current number of unmerged commits it > is taking long

[python-committers] Blocking commits to 2.6

2010-04-25 Thread Georg Brandl
Hi, to make my life easier, I'd like to block all unmerged commits in 2.6 that nobody will merge anyway. I use ``svnmerge avail --log`` to find out which commits I have to merge, and with the current number of unmerged commits it is taking longer and longer. Does anyone else use svnmerge integra