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/2011-March/108766.html below:

[Python-Dev] hg merge flow

[Python-Dev] hg merge flow [Python-Dev] hg merge flowAntoine Pitrou solipsis at pitrou.net
Sun Mar 6 00:57:56 CET 2011
On Sun, 06 Mar 2011 00:44:03 +0100
"Martin v. Löwis" <martin at v.loewis.de> wrote:
> How should patches be applied to the cpython repository if they
> land in more than one branch?
> 
> More specifically, assuming I want to patch all of 2.7, 3.1, 3.2, and
> default - how do I apply the patches and how do I merge?

(reposting my answer from another thread)

- on one hand: 2.5 -> 2.6 -> 2.7 (if you still want to maintain 2.5)
- on the other hand: 3.1 -> 3.2 -> default

Whether you start with 2.x or 3.x is unimportant.

Regards

Antoine.


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