Not quite the same: his repo is outdated (check out the tags), and has commits of his own that are not in SVN (e.g. https://github.com/JamesKovacs/nhibernate/commit/ba752881b3c005ba6ba32b1ebb08e2f52d65078e)
-- Mauricio On Tue, Aug 2, 2011 at 2:25 PM, Fabio Maulo <[email protected]> wrote: > The same from James > https://github.com/JamesKovacs/nhibernate > > > On Tue, Aug 2, 2011 at 1:35 PM, Mauricio Scheffer < > [email protected]> wrote: > >> If NHibernate decides to move to git, you might be interested in my >> github mirror: https://github.com/mausch/NHibernate , which contains >> of course the whole history, is up to date, and has all tags and >> branches. >> >> All that would be needed to complete the migration is mapping the >> committers to their proper github accounts (which isn't hard, just >> some filter-branches, doesn't take too long). So the slowest part >> (migrating the actual commits from SVN to git) is already done. >> >> Of course, tooling support is a separate issue. I don't know what >> tools NHibernate currently uses that depend on SVN (could be nant for >> tagging, TeamCity, JIRA integration, ...) >> >> Cheers, >> Mauricio >> >> On Aug 2, 3:32 am, Patrick Earl <[email protected]> wrote: >> > I agree with the points presented by Steve: >> > >> > * Migrate on 8/15. Will give us two weeks to experiment to ensure we >> > get the migration right. >> > * Use GitHub. >> > * Retain JIRA. >> > >> > I'm happy to help out wherever needed. I've spent significant time >> > with all of GIT, SVN, and JIRA. Does anyone around have a claim to >> > fame of being a GIT guru or successfully migrating from SVN? >> > >> > Are there any changes we'd want to make along the way to GIT? Should >> > the core and all support libraries (including things like Npgsql.dll >> > only used for testing) be part of a single repo? >> > >> > Patrick Earl >> > > > > -- > Fabio Maulo > >
