Re: hg2git error

From: Rocco Rutte <pdmef@gmx.net>
Date: May 25, 2009, 13:22 UTC
Message-ID: <20090525132242.GB3259@robert>
In-Reply-To: <alpine.DEB.1.00.0905251341370.4288@intel-tinevez-2-302>

Hi,

* Johannes Schindelin wrote:

> On Mon, 25 May 2009, Rocco Rutte wrote:
> > * Johannes Schindelin wrote:

> > > Error: repository has at least one unnamed head: hg r533

Show 6 quoted lines

> > I'm afraid there's nothing you can do except a) wait until somebody with
> > push access to the repo merges or b) do that yourself. The error means
> > that on a branch there's more than one head (i.e. childless
> > revision). There's no equivalent concept in git which is why I don't
> > know what to do. Generating fake branch names for git may be a little
> > messy I think.

> I disagree... The worst solution is to stop working at all.  A better 
> solution would be to ignore the unnamed head, and the best solution would 
> probably be to generate ref names that are _not_ branch names for such 
> heads.

Both solutions require refactoring and new code that is abled to walk the DAG mercurial gives us since in both cases we'd need to find the fork point. I don't know mercurials good enough to say if and how much its API can help here.

I don't use git any longer and do only fix obvious breakages for hg-fast-export, read: since this is a new feature I'm afraid I won't implement it.

Rocco