From: "Felipe Contreras" <felipe.contreras@gmail.com>
To: "Brian Downing" <bdowning@lavos.net>
Cc: git@vger.kernel.org, monotone-devel@nongnu.org
Subject: Re: [RFC] mtn to git conversion script
Date: Mon, 25 Aug 2008 23:47:53 +0300 [thread overview]
Message-ID: <94a0d4530808251347g4d6246bv7ebd5cc86294dd05@mail.gmail.com> (raw)
In-Reply-To: <20080825163530.GJ31114@lavos.net>
On Mon, Aug 25, 2008 at 7:35 PM, Brian Downing <bdowning@lavos.net> wrote:
> On Sun, Aug 24, 2008 at 12:18:50PM +0300, Felipe Contreras wrote:
>> I developed a script that converts a monotone repository into a git
>> one (exact clone), I want to contribute it so everybody can use it.
>>
>> This is the gist of the script:
>>
>> mtn update --revision #{@id} --reallyquiet
>> git ls-files --modified --others --exclude-standard -z | git
>> update-index --add --remove -z --stdin
>> git write-tree
>> git write-raw < /tmp/commit.txt
>> git update-ref refs/mtn/#{@id} #{@git_id}
>>
>> branches.each do |e|
>> git update-ref refs/heads/#{e} #{@git_id}
>> end
>
> You definitely want to use fast-import, but you probably want to do
> something a lot closer to fast-export for monotone (read: use its
> automate stdio interface and avoid expensive calls).
>
> Here's a simple monotone to git converter I wrote. You'll need the
> Monotone::AutomateStdio perl module to use it (which I think I got it
> from monotone's net.venge.monotone.contrib.lib.automate-stdio branch).
> It is very fast; it can convert the OpenEmbedded repo in something like
> 5-10 minutes on my machine.
Interesting, how many commits?
> Note that for monotone export to go fast you absolutely /must/ avoid the
> get_manifest operation. In my converter I use the revision information
> directly. Getting the renames right with this is a little tricky; IIRC,
> the ordering that works is:
>
> * Rename all renamed files, innermost files first, to temporary names.
> * Delete all deleted files, innermost first.
> * Rename all temporary names to permanent names, outermost first.
> * Add all new/modified files.
>
> Conveniently, all of the above can be done by directly emitting
> fast-import commands, so you don't have to keep track of trees directly.
> (With one exception, which I'll elaborate on in a different email.)
I guess I haven't stumbled upon that problem yet =/
Best regards.
--
Felipe Contreras
next prev parent reply other threads:[~2008-08-25 20:49 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-24 9:18 [RFC] mtn to git conversion script Felipe Contreras
2008-08-24 13:14 ` Miklos Vajna
2008-08-24 18:19 ` Johannes Schindelin
2008-08-24 19:37 ` Miklos Vajna
2008-08-24 18:33 ` Felipe Contreras
2008-08-24 22:46 ` Shawn O. Pearce
2008-08-25 0:45 ` Felipe Contreras
2008-08-28 5:57 ` Anand Kumria
2008-08-28 9:03 ` [Monotone-devel] " Felipe Contreras
2008-09-04 9:43 ` Felipe Contreras
2008-09-04 10:31 ` Jakub Narebski
2008-09-04 13:21 ` Felipe Contreras
2008-09-04 10:50 ` Thomas Moschny
2008-09-04 13:29 ` Felipe Contreras
2008-08-25 16:35 ` Brian Downing
2008-08-25 16:41 ` Brian Downing
2008-08-25 20:47 ` Felipe Contreras [this message]
2008-08-25 21:09 ` Brian Downing
2008-08-28 7:11 ` Anand Kumria
2008-11-11 16:30 ` Juan Jose Comellas
2008-11-11 16:40 ` Juan Jose Comellas
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=94a0d4530808251347g4d6246bv7ebd5cc86294dd05@mail.gmail.com \
--to=felipe.contreras@gmail.com \
--cc=bdowning@lavos.net \
--cc=git@vger.kernel.org \
--cc=monotone-devel@nongnu.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 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).