R. David Murray rdmurray at bitdance.com
Thu Jul 2 20:34:38 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 ]

---

On Fri, 3 Jul 2009 at 02:13, Anthony Baxter wrote:
> 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.

No, we have 2.7, 2.6, 3.2, and 3.1.

Using svnmerge to commit to three branches in addition to trunk
is...painful.  Because of the (lack of) speed.

--David

---

• 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