A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2013-August/128051.html below:

[Python-Dev] Status of 3.2 in Hg repository?

[Python-Dev] Status of 3.2 in Hg repository? [Python-Dev] Status of 3.2 in Hg repository?Barry Warsaw barry at python.org
Wed Aug 21 03:00:41 CEST 2013
On Aug 20, 2013, at 07:33 PM, Tim Peters wrote:

>So let's try a different question ;-)  Would anyone _object_ to
>completing the process described in the docs:  merge 3.2 into 3.3,
>then merge 3.3 into default?  I'd be happy to do that.  I'd throw away
>all the merge changes except for adding the v3,2.5 tag to .hgtags.
>
>The only active branches remaining would be `default` and 2.7, which
>is what I expected when I started this ;-)

That's what I'd expect to, so no objections from me.  But I'm only the lowly
2.6 RM and I will soon be rid of that particular albatross!  FWIW, I'm still
merging relevant 2.6 changes into 2.7 (or null merging them if not relevant).

Oh, and welcome back Uncle Timmy!  (If that's you're real name.)

-Barry
More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4