Both are better than the current for usability IMHO. But,

+1 for Option 1
(if I get the right to vote)

and I hope Option 1 will not cause a familiar never-ending-castle-1.0-RC
case :)

2011/6/23 hammett <[email protected]>

> 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.
>
>


-- 
Berke SOKHAN.

http://twitter.com/berkesokhan
http://blog.berkesokhan.com
http://www.birliktegelistir.com/editors.aspx

-- 
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.

Reply via email to