On Jul 19, 2012, at 3:54 PM, Kieran Kelleher wrote: > > On Jul 19, 2012, at 3:00 PM, Maik Musall wrote: > >> Hi, >> >> I'm about to migrate a large project which is currently managed in >> subversion to git. Git experience is still limited. Besides wonder >> frameworks, the project consists of >> >> - one application >> - several frameworks that are more or less specific to the application >> - several more generic frameworks that we use throughout the company in a >> number of apps. >> >> In subversion, all those are separate projects but on the same svn server. >> This enables commits spanning the app itself and all affected frameworks, >> for example to encapsulate one change that changes the API of a framework >> and adapts the app to that API change at the same time. >> >> What would the git freaks among you recommend as a repo layout for that? > > One svn server or one svn repo right now? > > IMHO, just do a one-to-one svn repo conversion and convert the svn history to > git history (plenty of articles showing how to do that, and it should be > straightforward if your svn layout was always the standard > trunk/branches/tags. > > > >> >> I don't think putting it all into one giant repo isn't an option because >> that would require all other projects (which are dozens) we have to be in it >> as well. That would not only be an unmanageable mess, but we couldn't pull >> off git migration for everything in one step anyway. > > As mentioned above, convert each svn repo to a git repo. You can even just do > that now yourself on your own machine to experiment and see what it looks > like. > > One popular process is to > (1) use svn-mirror to make a local svn mirror (clone?) of the svn repo and > then > (2) do a git-svn conversion clone on that (with a constructed authors file) > and then > (3) make a final svn-meta-data-free clone of that intermediate one. > > If all goes smoothly, you can write a script to update and maintain all three > intermediates
I meant until you are ready to flip the switch and go live committing to the pure-git-clone. Until then, it can be a read-only repo that people can "clone, play and learn" > > live-svn --> svn-mirrror --> git-svn-clone --> pure-git-clone > > Lots of articles on this if you do a google search. > > >> >> The other extreme would be separate repos for each app and each framework, >> but wouldn't that mean that we couldn't do combined commits any more across >> app and frameworks? Or is there another way to clarify for developers and >> build servers which framework commit they need to pull to match a specific >> app commit? >> >> What would you do? >> >> Thanks >> Maik >> _______________________________________________ >> Do not post admin requests to the list. They will be ignored. >> Webobjects-dev mailing list ([email protected]) >> Help/Unsubscribe/Update your Subscription: >> https://lists.apple.com/mailman/options/webobjects-dev/kelleherk%40gmail.com >> >> This email sent to [email protected] > _______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [email protected]
