[python-committers] Blocking commits to 2.6 (original) (raw)
Nick Coghlan ncoghlan at gmail.com
Mon Apr 26 03:38:00 CEST 2010
- Previous message: [python-committers] Blocking commits to 2.6
- Next message: [python-committers] When do we stop automerging from trunk to py3k?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
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 --logto 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 integration info on the 2.6 branch? Please speak up, so that I don't mess up your workflow.
I'd say go ahead - if anyone has a particular change that they want to backport, they can still do it manually (or else unblock it first).
Cheers, Nick.
-- Nick Coghlan | ncoghlan at gmail.com | Brisbane, Australia
- Previous message: [python-committers] Blocking commits to 2.6
- Next message: [python-committers] When do we stop automerging from trunk to py3k?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]