[prev in list] [next in list] [prev in thread] [next in thread]
List: python-dev
Subject: Re: [Python-Dev] Mercurial conversion repositories
From: Santoso Wijaya <santoso.wijaya () gmail ! com>
Date: 2011-02-26 18:56:59
Message-ID: AANLkTimbZuLiAjM5FcberrL20ULquxGbjA_1-ZVK8V1t () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
>From http://mercurial.selenic.com/wiki/Branch#Named_branches:
[...] a good rule of thumb is to use branch names sparingly and for rather
longer lived concepts like "release branches" (rel-1, rel-2, etc) and rather
not for short lived work of single developers
So I think named branches make sense here. Bookmarks are really for
potential branches, experimental features, for example, for easier
navigation for the developer's convenience. Named branches, on the other
hand, are better for posterity reasons.
~/santa
On Sat, Feb 26, 2011 at 10:40 AM, Daniel Stutzbach <stutzbach@google.com>wrote:
> On Sat, Feb 26, 2011 at 9:55 AM, Antoine Pitrou <solipsis@pitrou.net>wrote:
>
>> There is no such thing as an "unnamed branch". What would "hg branches"
>> show? An empty space?
>>
>
> I understand now why I was confused. I had previously read the sentence
> "Both Git and Mercurial support unnamed local branches." at
> http://mercurial.selenic.com/wiki/BranchingExplained
>
> But as I dig deeper, I see that there is only one unnamed branch, and it
> actually does have an implicit name: "default".
>
> It appears Mercurial supports at least three different kinds of branching:
> cloning (similar to Bazaar), bookmarks (similar to git), and named branches.
> So a named branch can contain more than one branch.
>
> Were there reasons for going with named branches over bookmarks? PEP 385
> discusses only cloning and named branches. I'm just curious, not trying to
> start a long discussion. :-)
>
> --
> Daniel Stutzbach
>
> _______________________________________________
> Python-Dev mailing list
> Python-Dev@python.org
> http://mail.python.org/mailman/listinfo/python-dev
> Unsubscribe:
> http://mail.python.org/mailman/options/python-dev/santoso.wijaya%40gmail.com
>
>
[Attachment #5 (text/html)]
<div>From <a href="http://mercurial.selenic.com/wiki/Branch#Named_branches">http://mercurial.selenic.com/wiki/Branch#Named_branches</a>:<br \
clear="all"></div><div><br></div><div style="margin-left: 40px">[...] a good rule of \
thumb is to use branch names sparingly and for rather longer lived concepts like \
"release branches" (rel-1, rel-2, etc) and rather not for short lived work \
of single developers</div>
<div style="margin-left: 40px"><br></div><div style="margin-left: 0px">So I think \
named branches make sense here. Bookmarks are really for potential branches, \
experimental features, for example, for easier navigation for the developer's \
convenience. Named branches, on the other hand, are better for posterity \
reasons.</div>
<div><br></div>~/santa<br>
<br><br><div class="gmail_quote">On Sat, Feb 26, 2011 at 10:40 AM, Daniel Stutzbach \
<span dir="ltr"><<a \
href="mailto:stutzbach@google.com">stutzbach@google.com</a>></span> \
wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px \
#ccc solid;padding-left:1ex;">
<div class="gmail_quote"><div class="im">On Sat, Feb 26, 2011 at 9:55 AM, Antoine \
Pitrou <span dir="ltr"><<a href="mailto:solipsis@pitrou.net" \
target="_blank">solipsis@pitrou.net</a>></span> wrote:<br><blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex">
There is no such thing as an "unnamed branch". What would "hg \
branches"<br> show? An empty space?<br></blockquote><div><br></div></div><div>I \
understand now why I was confused. I had previously read the sentence "Both \
Git and Mercurial support unnamed local branches." at <a \
href="http://mercurial.selenic.com/wiki/BranchingExplained" \
target="_blank">http://mercurial.selenic.com/wiki/BranchingExplained</a></div>
<div><br></div><div>But as I dig deeper, I see that there is only one unnamed branch, \
and it actually does have an implicit name: \
"default".</div><div><br></div><div>It appears Mercurial supports at least \
three different kinds of branching: cloning (similar to Bazaar), bookmarks (similar \
to git), and named branches. So a named branch can contain more than one \
branch.</div>
<div><br></div><div>Were there reasons for going with named branches over bookmarks? \
PEP 385 discusses only cloning and named branches. I'm just curious, not trying \
to start a long discussion. :-)</div></div><br>-- <br>
<font color="#888888">
Daniel Stutzbach<br>
</font><br>_______________________________________________<br>
Python-Dev mailing list<br>
<a href="mailto:Python-Dev@python.org">Python-Dev@python.org</a><br>
<a href="http://mail.python.org/mailman/listinfo/python-dev" \
target="_blank">http://mail.python.org/mailman/listinfo/python-dev</a><br>
Unsubscribe: <a href="http://mail.python.org/mailman/options/python-dev/santoso.wijaya%40gmail.com" \
target="_blank">http://mail.python.org/mailman/options/python-dev/santoso.wijaya%40gmail.com</a><br>
<br></blockquote></div><br>
_______________________________________________
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: http://mail.python.org/mailman/options/python-dev/python-dev%40progressive-comp.com
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic