[python-committers] Why r69846 is not merged to "release26-maint"?

[Anthony Baxter]

The particulars of the revision control system don't matter as much as the
discipline of teaching people to commit fixes. Right now, we have 2.6.x,
3.0.x and 3.1.x.

On Fri, Jul 3, 2009 at 1:22 AM, Jeroen Ruigrok van der Werven <
asmodai at in-nomine.org> wrote:

> -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.
>
> --
> Jeroen Ruigrok van der Werven <asmodai(-at-)in-nomine.org> / asmodai
> イェルーン ラウフロック ヴァン デル ウェルヴェン
> http://www.in-nomine.org/ | http://www.rangaku.org/ | GPG: 2EAC625B
> When you do something, you should burn yourself completely, like a good
> bonfire, leaving no trace of yourself...
> _______________________________________________
> python-committers mailing list
> python-committers at python.org
> http://mail.python.org/mailman/listinfo/python-committers
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-committers/attachments/20090703/49c0f91b/attachment.htm>