[python-committers] Guidance on merging(?)

2016-05-08 Thread Steven D'Aprano
Hi, My hg skills are still fairly basic, and I'm looking for somebody who can mentor me (or at least point me in the right direction) with respect to making the same change across multiple versions of Python. I have just made a one-line change to the 3.6 (default) branch: https://hg.python.org

Re: [python-committers] Guidance on merging(?)

2016-05-08 Thread Berker Peksağ
On Sun, May 8, 2016 at 4:18 PM, Steven D'Aprano wrote: > Hi, > > My hg skills are still fairly basic, and I'm looking for somebody who > can mentor me (or at least point me in the right direction) with respect > to making the same change across multiple versions of Python. > > I have just made a o

Re: [python-committers] Guidance on merging(?)

2016-05-08 Thread Serhiy Storchaka
2016-05-08 16:18 GMT+03:00 Steven D'Aprano : > My hg skills are still fairly basic, and I'm looking for somebody who > can mentor me (or at least point me in the right direction) with respect > to making the same change across multiple versions of Python. > > I have just made a one-line change to t

Re: [python-committers] Guidance on merging(?)

2016-05-08 Thread Jesus Cea
On 08/05/16 15:31, Serhiy Storchaka wrote: > For future, you should first commit your patch in 3.5, and then merge > it in default. Yes, for the future, you should write the patch for the oldest branch appropriate and then just merge it to the next branches. Let's say you have a security fich for

Re: [python-committers] Guidance on merging(?)

2016-05-08 Thread Brett Cannon
On Sun, 8 May 2016 at 06:30 Berker Peksağ wrote: > On Sun, May 8, 2016 at 4:18 PM, Steven D'Aprano > wrote: > > Hi, > > > > My hg skills are still fairly basic, and I'm looking for somebody who > > can mentor me (or at least point me in the right direction) with respect > > to making the same ch