From: Alex Riesen Date: Thu, 12 Jan 2006 08:58:23 GMT Subject: Re: RFC: Subprojects Message-ID: <81b0412b0601120058u6e60f009u5caf83ba574aaa7e@mail.gmail.com> In-Reply-To: <200601121436.52827.lan@ac-sw.com> On 1/12/06, Alexander Litvinov wrote: > > > 1. I need to have ability to make tags, branches thru all subprojects. > > > > I suspect that this is a bad idea -- for the same reason as committing > > to a subproject is a bad idea. The subprojects most likely have their > > own external repositories -- and lifecycles of their own. The same > > headname/branchname won't do. > > This is one main idea of supporing subprojects. Everything else I already can > do. I want to be able to make tag over composite project and be able to fetch > tagged files later. The same with branches. > > I cleary understand if I made tag/branch on subproject outside my composite > project I will not be able to work with it - this is ok. > > But tag/branches on whole composite project is "the must". The Linus' proposal of gitlink will probably help you here: gitlink will be tagged as well, so you just have to teach git-checkout about checking out subprojects.