Re: [RFC] [PATCH 0/5] Implement 'prior' commit object links
- From
Jakub Narebski <jnareb@gmail.com>
- Date
- Apr 26, 2006, 07:22 UTC
- Message-ID
- <e2n72h$aqe$1@sea.gmane.org>
- In-Reply-To
- <7vlktssudl.fsf_-_@assigned-by-dhcp.cox.net>
Junio C Hamano wrote:
Show 13 quoted lines
> (On topic again) > > Link from subproject commit back to the toplevel might work for > some kind of subprojects, but it would not work for the > subproject support that frequently comes up on this list. The > development of an embedded Linux device, where a Linux kernel > source tree is grafted at kernel/ subdirectory of the toplevel > project. The "prior" link would be placed in the commit that > belong to the kernel subproject, but that would never be merged > to the Linus kernel (why should he care about one particular > embedded device's development history). The link must go from > the toplevel to generic parts reusable out of the context of the > combined project.
Yes, I guess subproject support is most needed for the "third-party embedded (sub)project", when one sometimes have to modify (sub)project files, and perhaps have to watch for the (sub)project version. Hmmm... if one used Tailor (to allow for projects not managed under GIT, though I wonder if it would be possible to link up project without [externally available] SCM) one could use this approach for managing distribution packages, like RPMS or debs...
Do I understand correctly that toplevel (master project) commits have tree which points to combined tree, and "bind" links which points to the subprojects commits whose trees make up the overall tree, or does the master tree points to tree containing only toplevel files (overall Makefile for example, INSTALL or README for the whole project including subprojects,...)?
BTW. I have lately stumbled upon (somewhat Vault and Subversion biased) http://software.ericsink.com/Beyond_CheckOut_and_CheckIn.html Read about Share and Pin -- it's about subprojects (when you edit out the flawed "branch as folder" approach of author). I wonder if it could be easily implemented in "subprojects for GIT" proposal... Of course we can do better, i.e. original subproject repository doesn't need to be on the same machine, we can use remote repository.
-- Jakub Narebski Warsaw, Poland