Re: [Python-Dev] of branches and heads

2011-02-27 Thread Daniel Stutzbach
On Sun, Feb 27, 2011 at 2:42 AM, Adrian Buehlmann wrote: > On 2011-02-26 23:26, Greg Ewing wrote: > > There are *some* topological restrictions, because hg won't > > let you assign a branch name that's been used before to a node > > unless one of its parents has that name. So you can't create > >

Re: [Python-Dev] of branches and heads

2011-02-27 Thread Adrian Buehlmann
On 2011-02-26 23:26, Greg Ewing wrote: > From: Antoine Pitrou >> - a "branch" usually means a "named branch": a set of changesets >> bearing the same label (e.g. "default"); that label is freely chosen >> by the committer at any point, and enforces no topological >> characteristic > > There

Re: [Python-Dev] of branches and heads

2011-02-26 Thread Martin v. Löwis
> So, actually, hg promotes a slightly different terminology: > - a "head" is a changeset without a child in the topology So what do you call the LoD leading up to a head? (i.e. the set of changesets that are ancestors of a head and not ancestors of any other head) Regards, Martin _

Re: [Python-Dev] of branches and heads

2011-02-26 Thread Greg Ewing
From: Antoine Pitrou > - a "branch" usually means a "named branch": a set of changesets > bearing the same label (e.g. "default"); that label is freely chosen > by the committer at any point, and enforces no topological > characteristic There are *some* topological restrictions, because hg w