Insights from bzr newbie coming from git
Matthew D. Fuller
fullermd at over-yonder.net
Mon Dec 4 23:50:30 GMT 2006
On Sat, Dec 02, 2006 at 11:02:01AM +0100 I heard the voice of
Jan Hudec, and lo! it spake thus:
>
> Since branch is a pointer to head (and just that) by definition, it
> would not be multiple heads per *branch*. And we *can* have multiple
> heads per repository (which is the same monotone and mercurial do --
> they don't have a concept of a branch at all, only a checkout and a
> repository).
In the case of monotone, you _can_ have multiple heads in a branch,
which is what lets you have that sort of fun. I don't fully grok all
the details of monotone's "branch" concept; it seems that it's
generally ancestry based, _except_ when you start doing weird things
with certs (so you can have a rev "on a branch" that's totally
unrelated to any other rev on the branch, or revs on the branch
without their ancestors being on it, etc).
> All we need to create a Branch is a revision-id and a repository to
> fetch it from (apart from that a BzrBranch has revision-history,
> which is just a cache, and a nick, which this "ultralight" branch
> does not need).
I would say it should have the same nick as its parent branch, in this
usage.
--
Matthew Fuller (MF4839) | fullermd at over-yonder.net
Systems/Network Administrator | http://www.over-yonder.net/~fullermd/
On the Internet, nobody can hear you scream.
More information about the bazaar
mailing list