From: Rocco Rutte <pdmef@gmx.net>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Matthias Urlichs <smurf@smurf.noris.de>, git@vger.kernel.org
Subject: Re: hg2git error
Date: Mon, 25 May 2009 15:22:42 +0200 [thread overview]
Message-ID: <20090525132242.GB3259@robert> (raw)
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
> > 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
prev parent reply other threads:[~2009-05-25 13:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-24 17:33 hg2git error Johannes Schindelin
2009-05-24 17:38 ` Sverre Rabbelier
2009-05-24 18:16 ` Johannes Schindelin
2009-05-24 18:20 ` Sverre Rabbelier
2009-07-22 17:47 ` Johannes Schindelin
2009-07-22 18:05 ` Sverre Rabbelier
2009-05-25 11:34 ` Rocco Rutte
2009-05-25 11:43 ` Johannes Schindelin
2009-05-25 11:57 ` Matthieu Moy
2009-05-25 13:22 ` Rocco Rutte [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090525132242.GB3259@robert \
--to=pdmef@gmx.net \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=smurf@smurf.noris.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).