From: Felipe Contreras Date: Mon, 25 Aug 2008 00:45:11 GMT Subject: Re: [RFC] mtn to git conversion script Message-ID: <94a0d4530808241745r3f2bdb56q9cfa8bc61f79223e@mail.gmail.com> In-Reply-To: <20080824224658.GA16590@spearce.org> On Mon, Aug 25, 2008 at 1:46 AM, Shawn O. Pearce wrote: > Felipe Contreras wrote: >> On Sun, Aug 24, 2008 at 4:14 PM, Miklos Vajna wrote: >> > On Sun, Aug 24, 2008 at 12:18:50PM +0300, Felipe Contreras wrote: >> >> What do you think? Does it makes sense to have a 'write-raw' command? >> >> Or should I somehow use 'fast-import'? >> > >> > Yes, you should. ;-) >> > >> > The syntax of it is not so hard, see for example 'git fast-export >> > HEAD~2..' on a git repo and you'll see. >> > >> > This should help a lot if you are like me, who likes to learn from >> > examples. >> >> Is it possible to create a fast-import from the index? I realize this >> is not the best thing to do, but for now I would like to do that. > > No, fast-import uses its own internal structure and avoids the > index file. Yeah, I knew that, but wanted to just replace the 'write-raw' command. To avoid doing unnecessary changes. > Also, look at `git-hash-objects -w` as a replacement for your > git-write-raw tool if you aren't going to use git-fast-import. Awesome, but I just did it properly :) A few comments regarding fast-import: Why the distinction between 'from' and 'merge'? Doesn't it make more sense to use 'parent' for both? I'm doing: commit refs/mtn/d137c7046bae7e4a0144fee82bfce8061f61e3b3 So I was expecing this to work: from mtn/d137c7046bae7e4a0144fee82bfce8061f61e3b3 But it didn't, probably because the commit hasn't actually been committed. Wouldn't it make sense to store it as a temporal commit so my script doesn't have to deal with that? Anyway, very nice tool. It's going much faster (1h) compared to before (1 day). Best regards. -- Felipe Contreras