All of lore.kernel.org
 help / color / mirror / Atom feed
From: Han-Wen Nienhuys <hanwen@xs4all.nl>
To: git@vger.kernel.org
Cc: clee@kde.org
Subject: Re: darcs2git.py - convert darcs repository using gfi
Date: Tue, 13 Feb 2007 23:42:14 +0100	[thread overview]
Message-ID: <45D23EC6.9000806@xs4all.nl> (raw)
In-Reply-To: <20070212011401.GK31488@spearce.org>

Shawn O. Pearce escreveu:
>> The python script attached is a try at providing a sane
>> conversion from Darcs to GIT.  It tries to map darcs conflict
>> resolutions onto git branch merges.
> 
> Impressive.

If anyone's interested I've hacked at it some more, 
and the result is at 

  http://repo.or.cz/w/darcs2git.git

I've further improved the script so it generates nicer 
bifurcations, and does the conversion more incrementally as 
possible, and can be considered fast (as far as any darcs project
can be called fast) 

I've successfully converted a project containing
3000 patches with it.  

> This is harder than it sounds.  fast-import internally is built
> around the assumption of a branch, which has a name, and which lives
> in the branch LRU.  With the "from" command restriction lifted
> you can just import every single commit onto the same hardcoded
> branch name (e.g. DARCS_HEAD) then delete it when you are done
> (e.g. rm .git/DARCS_HEAD).  That's basically the same thing as an

will this be in git v1.5 ?

-- 
 Han-Wen Nienhuys - hanwen@xs4all.nl - http://www.xs4all.nl/~hanwen

  reply	other threads:[~2007-02-13 22:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-11 23:56 darcs2git.py - convert darcs repository using gfi Han-Wen Nienhuys
2007-02-12  1:14 ` Shawn O. Pearce
2007-02-13 22:42   ` Han-Wen Nienhuys [this message]
2007-02-18 12:45   ` git-fast-export ? Han-Wen Nienhuys
2007-02-19  8:25     ` Shawn O. Pearce

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=45D23EC6.9000806@xs4all.nl \
    --to=hanwen@xs4all.nl \
    --cc=clee@kde.org \
    --cc=git@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.