|
From: Michael B. <mb...@gm...> - 2011-07-25 10:29:42
|
On Sun, Jul 24, 2011 at 06:27:38PM -0400, Chris Frey wrote: > On Sun, Jul 24, 2011 at 10:53:51PM +0100, Paul Eggleton wrote: > > > How far back does your repo go? My earliest commits from SVN are: > > > > Hrm, I think I was going by your earlier comments; that's as far back as > > my history goes as well. > > My understanding and my explanation were likely lacking. :-) > > There's a truly huge commit in my repo at: > > commit 6c79ce53bd3dd15b60e51262fd02109c172d5bfa > Author: dgollub <dgollub@53f5c7ee-bee3-0310-bbc5-ea0e15fffd5e> > Date: Mon Feb 12 12:25:19 2007 +0000 > > Moved dev-branch to trunk... > Time to work on 0.30 ;) > > > git-svn-id: http://svn.opensync.org/trunk@1732 53f5c7ee-bee3-0310-bbc5-ea0e1 > 5fffd5e > > > This is the commit where the history of many files suddenly "ends". > But it seems to me that there should be history for some of those > files from before that. > > I'm assuming that "dev-branch" is where this work occurred, and it > was all merged in at once, and so some of these files appear suddenly, > "fully formed". > > I'm not sure if it is worth trying to extract that dev-branch from SVN, > since we can have an old read-only SVN repo for historical reference > even after the move to git. > > But even so, it might be interesting to do just a git-svn clone of > the dev-branch only, and then add that as a historical git branch > for reference. Honestly, I do not think this is time worth spent right now. If there were tons of developers with loads of time on their hands, it would certainly be worthwhile, but at this point, just doing a halfway sane migrations followed by continued development looks like a better investment of developer time to me. >From the sidelines, Michael |