hgweb page with hg log -b <branchname>

Mads Kiilerich mads at kiilerich.com
Sat Jan 9 17:34:32 CST 2010


Johan Samyn wrote, On 01/09/2010 10:28 AM:
> 2010/1/9 Mads Kiilerich<mads at kiilerich.com>:
>    
>> FWIW I had DAG branches in mind, not named branches. That makes a
>> difference, but they might have a lot in common anyway.
>>
>>      
> Mads, could you explain to me what you mean by the difference between
> a named branch and a DAG branch ?

I just to distinguish from "named branch". See 
http://mercurial.selenic.com/wiki/Branch for a description of how the 
term branch is sometimes used for slightly different concepts. "Named 
branch" is one of them and well-defined, but the alternative has no good 
name. I used "DAG branch" to describe - it might be a new and ugly term, 
but it is exact and Dan intuitively understood it ;-)

For various irrelevant reasons I don't like and don't use named branches.

> For example (letters respresent
> revision numbers obviously) :
> A - B - C - D - F - G - K (default)
>              \
>               E - H - I - J (feature1)
> To me a (named) branch is simply the group E-H-I-J (or even
> A-B-C-D-F-G-K), which was given a name that is registered in each cset
> along that line.
> Can you show me an example of what you mean by a DAG branch in the
> above example ?
>    

A shorter and less detailed example than Dans could be

A - B - C - D - F - G - K (default)
             \
              E - H - I - J (feature1)
                   \
                    L - M   (feature1)


where you have both the I-J and the L-M "branch" on your feature1 
"branch". And if you forget about the named branches in this example you 
have 3 "branches". These branches in the (Directed Asyclic) Graph is 
what I call "DAG branches". As you can see they occur both with and 
without named branches.

/Mads


More information about the Mercurial-devel mailing list