[python-committers] When do we stop automerging from trunk to py3k? (original) (raw)
Antoine Pitrou solipsis at pitrou.net
Wed Apr 28 12:17:38 CEST 2010
- Previous message: [python-committers] When do we stop automerging from trunk to py3k?
- Next message: [python-committers] When do we stop automerging from trunk to py3k?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Le mercredi 28 avril 2010 à 04:37 +0200, Jesus Cea a écrit :
That is, patch 2.7 and "push" those changes to 3.x, undoing the unnecesary patches with a simple "backout".
Good point. I haven't thought of the possibility of using "hg backout". However, those bugfixes must also be applied (usually) to 3.1, which makes the workflow graph a bit uncertain: (3.1 -> 2.7) and (3.1 -> 3.x)?
Regards
Antoine.
- Previous message: [python-committers] When do we stop automerging from trunk to py3k?
- Next message: [python-committers] When do we stop automerging from trunk to py3k?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]