Summarized from several messages
Steve Borho writes:
> 0.9 can't see the named branches so you got the tipmost head instead,
> which just happens to be a closed branch.
> I just cloned this locally with a recent Mercurial release and it did
> check out 840f66c02892, which is the tip of the default branch. The
> other heads are defunct CVS branches. This looks like a very recent
> cvs2hg conversion without any new Mercurial commits made to it. As
> soon as someone makes a commit to the mainline, the tip will be a
> useful revision.
> > What should I do to get the working copy ?
> hg up --clean 840f66c02892
So, anyone who uses hg 0.9 to clone the clisp repository before any
new commits should to the command above.
> Pull never changes the branch that you are currently on. In fact it
> doesn't change your working parent at all. You have to update after
> pulling to move forward on your branch (or use the 'hg pull --update'
> shortcut). Either way, the update will stay on the current branch.
> What bit you on this initial clone is that 0.9 is unaware of closed
> heads so it didn't know to pick the only active one.
So I'm now assuming that the "current clisp source" will remain
on the current branch forever (as long as we use hg). If this
assumption is ever violated, please warn us.
Get latest updates about Open Source Projects, Conferences and News.