I need some clarification on opt1, is this master repository only for when we need to do some integration tests? So, we would keep on using the current repositories as we are now, but if we run into integration issues that are hard to debug we then would pull the "master repository", is this what you mean by opt 1?
Cheers John ________________________________ From: hammett <[email protected]> To: [email protected] Sent: Friday, 24 June 2011 5:14 AM Subject: Re: [Vote] Submodules vs Aggregation of some repositories Okay, rephrasing the options: Option 1: Create a master project that include all other ones as git-subtrees Option 2: Aggregate some as suggested by Krzysztof On Thu, Jun 23, 2011 at 11:25 AM, Ayende Rahien <[email protected]> wrote: > Submodules are bad, in my experience. They result in a cloned repository > that can't immediately be used without extra work, that is additional > support cost > I am using git subtree to handle those things, and it works pretty nicely. -- Cheers, hammett http://hammett.castleproject.org/ -- You received this message because you are subscribed to the Google Groups "Castle Project Development List" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/castle-project-devel?hl=en. -- You received this message because you are subscribed to the Google Groups "Castle Project Development List" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/castle-project-devel?hl=en.
