Re: [SVN-MIGRATION] Re: Github
[email protected] (Johannes Schlüter) Thu, 26 Feb 2009 00:41:39 +0100
| Newsgroups | svn.migration |
|---|---|
| Message-ID | <1235605299.5774.120.camel@goldfinger> |
On Wed, 2009-02-25 at 15:19 -0800, shire wrote: > > http://git.chinstrap.eu/php/php-tsrm-ze2.git/ > > > > Looks quite good as a start, compiles nicely on all active branches. But > > didn't check all parts of the history. > > > > HUh, are you importing this with the git-cvsimport tools? I had been > doing this myself for a while and when we started 5.3 I started > noticing differences between GIT and CVS HEAD. Looks like I emailed > David Soria Parra about this and some other bugs (included excerpt > below). Maybe some of these issues have been fixed? (crosses fingers) I'm rsyncing the ,v file and then using parsecvs with some fixes from David and me. http://git.chinstrap.eu/?p=parsecvs.git;a=summary Not sure if they went upstream - I mailed the original author but didn't track that. There is one issue with these trees though: I always rebuild the whole tree and for some reason the revision SHA-1s don't match so when pulling every now and then changes from the master gives you a new branch starting somewhere in the past looking mostly the same (with the latest stuff added) I think that's somehow related to the phar fix (didn't see that before) but didn't investigate - but that won't matter if we go the git-route as in the end we'd do one conversion and set cvs to read-only and don't update from cvs.... (and for my current main use it doesn't matter that much - I'm mostly using it or browsing patch sets when reviewing commits ... that works way better than with commit mails or cvsps-based tools) johannes