git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [RFC] mtn to git conversion script

From
Felipe Contreras <felipe.contreras@gmail.com>
Date
Aug 25, 2008, 20:47 UTC
Message-ID
<94a0d4530808251347g4d6246bv7ebd5cc86294dd05@mail.gmail.com>
In-Reply-To
<20080825163530.GJ31114@lavos.net>
On Mon, Aug 25, 2008 at 7:35 PM, Brian Downing <bdowning@lavos.net> wrote:
Show 26 quoted lines
> 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?
Show 13 quoted lines
> 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
Previous: Brian DowningNext: Brian Downing
Message 17 of 21 in “[RFC] mtn to git conversion script”
  1. Felipe ContrerasAug 24, 2008
  2. Miklos VajnaAug 24, 2008
  3. Johannes SchindelinAug 24, 2008
  4. Miklos VajnaAug 24, 2008
  5. Felipe ContrerasAug 24, 2008
  6. Shawn O. PearceAug 24, 2008
  7. Felipe ContrerasAug 25, 2008
  8. Anand KumriaAug 28, 2008
  9. Felipe ContrerasAug 28, 2008
  10. Felipe ContrerasSep 4, 2008
  11. Jakub NarebskiSep 4, 2008
  12. Felipe ContrerasSep 4, 2008
  13. Thomas MoschnySep 4, 2008
  14. Felipe ContrerasSep 4, 2008
  15. Brian DowningAug 25, 2008
  16. Brian DowningAug 25, 2008
  17. Felipe ContrerasAug 25, 2008
  18. Brian DowningAug 25, 2008
  19. Anand KumriaAug 28, 2008
  20. Juan Jose ComellasNov 11, 2008
  21. Juan Jose ComellasNov 11, 2008

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.