Re: RFC: Subprojects
- From
- Josef Weidendorfer <josef.weidendorfer@gmx.de>
- Date
- Jan 16, 2006, 10:44 UTC
- Message-ID
- <200601161144.48245.Josef.Weidendorfer@gmx.de>
- In-Reply-To
- <7vek3ah8f9.fsf@assigned-by-dhcp.cox.net>
On Saturday 14 January 2006 21:16, you wrote:
Show 7 quoted lines
> Yes, I agree to the above 100%; the serious disadvantages come > from the fact that we do not have clear separation between > subprojects -- which new files belong to what subproject. I > ... > - Extend "commit" objects for the toplevel project to record > what subprojects with what head commits are contained at > which subdirectory.
The suggested "bind" info in commit objects has the same problem as the original overlay: if the superproject already has a subdirectory kernel/, and there is an additional "bind" specification in commits also for kernel/, what should be done?
So the gitlink object seems to be the only solution if we want to bind git versions of subprojects into a superproject.
But as this seems to make everything quite complex and not-obvious for a user, I am with Paskys simple subproject idea.
Josef