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-February/108364.html below:

[Python-Dev] Mercurial conversion repositories

[Python-Dev] Mercurial conversion repositories [Python-Dev] Mercurial conversion repositoriesAntoine Pitrou solipsis at pitrou.net
Sat Feb 26 18:32:26 CET 2011
Le samedi 26 février 2011 à 09:27 -0800, Daniel Stutzbach a écrit :
> On Sat, Feb 26, 2011 at 8:44 AM, Antoine Pitrou <solipsis at pitrou.net>
> wrote:
>         Le samedi 26 février 2011 à 08:38 -0800, Daniel Stutzbach a
>         écrit :
>         
>         > Can we just get rid of "trunk" altogether?  It's history is
>         a strict
>         > subset of the 2.7 branch's history, isn't it?
>         
>         
>         Named branches are exclusive, they can't be a subset of each
>         other ;)
>         (in other words: 2.7 starts where trunk stops; trunk
>         changesets are
>         strict ancestors of 2.7)
> 
> 
> Maybe I don't fully understand how Mercurial branches work or how it
> defines terminology (in fact, that is likely :) ).  What's the
> difference between the statement "trunk changesets are strict
> ancestors of 2.7" and the statement "trunk's history is a strict
> subset of 2.7's history"?

Apparently you overlooked the first statement:
"Named branches are exclusive".
In other words, a changeset can be in only one named branch.
So it's impossible for a branch to be a subset or superset of another.
(except the trivial case of an empty branch :-)).



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