Git repo layout for own WO projects
Git repo layout for own WO projects
- Subject: Git repo layout for own WO projects
- From: Maik Musall <email@hidden>
- Date: Thu, 19 Jul 2012 21:00:44 +0200
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?
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.
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@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden