Re: Converting to Git using svn-fe (Was: Speeding up the initial git-svn fetch)
- From
Sverre Rabbelier <srabbelier@gmail.com>
- Date
- Oct 15, 2010, 23:39 UTC
- Message-ID
- <AANLkTim6w54CPhw0GzaDxT9e0t19XQ7-rMEe5aSBevS+@mail.gmail.com>
- In-Reply-To
- <2196050.492435.1287154246295.JavaMail.root@mail.hq.genarts.com>
Heya,
On Fri, Oct 15, 2010 at 09:50, Stephen Bash <bash@genarts.com> wrote:
> The process can certainly be streamlined. As is often the case, this > process was created via the "just make it work" mentality (and a barely > passable knowledge of git).
Fair enough :)
> But I'm also looking at this from a one-time conversion view. I had a > couple of conversations with Ram that showed me my point of view is > very narrow compared to the larger git-remote-svn effort...
Yeah, we not only want 'git-remote-svn' to be able to do incremental imports, but we also want it to be able to push back to svn.
Show 5 quoted lines
> I think using notes is a better way to associate conversion information > with commits, but I would probably still end up mining the notes to create > some sort of svn to git mapping... Correct me if I'm wrong, but I don't see > how notes would help me get from an svn rev to a git sha (a common > practice for tickets and wiki links in our organization).
Ah, hmm, that is a good point. Couldn't you just tag object 0000000000000000143 for svn revision 143?
> I guess after that I should add that I'm happy to help, I'm just not sure > where my experience maps to the on going effort.
Just general feedback, sanity checking, and if you're interested, "beta testing" I think would be very useful :).
-- Cheers, Sverre Rabbelier