Re: [RFC] [PATCH 0/5] Implement 'prior' commit object links

From: Junio C Hamano <junkio@cox.net>
Date: Apr 26, 2006, 06:50 UTC
Message-ID: <7vlktssudl.fsf_-_@assigned-by-dhcp.cox.net>
In-Reply-To: <e2n4am$1vn$1@sea.gmane.org>

Jakub Narebski <jnareb@gmail.com> writes:

Show 16 quoted lines

> Junio C Hamano wrote:
>
>> Jakub Narebski <jnareb@gmail.com> writes:
>> 
>>> Jakub Narebski wrote:
>>>
>>>> [...] Sam's "prior (3)" example
>>>> link would point to the toplevel project (gathering all subprojects)
>>>> commit, and it would probably be named/noted "toplevel", not "prior".
>>>
>>> Or "master" (like "master document" in DTP).
>> 
>> (Offtopic) isn't "master" in DTP more like template?
>
> Well, in (La)TeX "master document" is a document on it's own rights,
> subdocuments are transcluded using some kind of "include"-like command.

(Offtopic) Ah, the hard-core stuff. I had something else in mind ("master page" in "DTP for dummies"), sorry for the confusion.

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