[python-committers] Why r69846 is not merged to "release26-maint"?
Benjamin Peterson
benjamin at python.org
Thu Jul 2 17:23:41 CEST 2009
More information about the python-committers mailing list
Thu Jul 2 17:23:41 CEST 2009
- Previous message: [python-committers] Why r69846 is not merged to "release26-maint"?
- Next message: [python-committers] Why r69846 is not merged to "release26-maint"?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
2009/7/2 Jeroen Ruigrok van der Werven <asmodai at in-nomine.org>: > -On [20090702 17:15], Jesus Cea (jcea at jcea.es) wrote: >>Ughhh. This is actually a good reason to migrate to mercurial, were >>merges are painless :-). > > For all I know Mercurial doesn't make the issue of resolving content merges > easier, so that would make your comment moot. They're about 2^987987979 times faster, though than with svnmerge.py. -- Regards, Benjamin
- Previous message: [python-committers] Why r69846 is not merged to "release26-maint"?
- Next message: [python-committers] Why r69846 is not merged to "release26-maint"?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the python-committers mailing list