Re: [RFC] New commit object headers: generation and note headers

From: Junio C Hamano <gitster@pobox.com>
Date: Feb 9, 2008, 21:03 UTC
Message-ID: <7vlk5tetaa.fsf@gitster.siamese.dyndns.org>
In-Reply-To: <fcaeb9bf0802090950l27aa247ei5d067e0f24fcade0@mail.gmail.com>

"Nguyen Thai Ngoc Duy" <pclouds@gmail.com> writes:

Show 15 quoted lines

> On Sun, Feb 10, 2008 at 12:35 AM, Daniel Barkalow <barkalow@iabervon.org> wrote:
>>
>> On Sat, 9 Feb 2008, Jakub Narebski wrote:
>>  > 2. 'note' header (no semantical meaning)
>>  >
>>  > There was some time ago discussion about adding 'note' header, initially
>>  > to save original sha-1 of a commit for cherry-picking and rebase; then
>>  > for saving explicit rename or corrected rename info, for saving chosen
>>  > merge strategy, and for saving original ID of SCM import.
>>
>>  Probably want to have a prescribed syntax for specifying what note this
>>  is, so that different programs using notes don't confuse each other.
>
> How about git ignoring all X- headers and let programs freely add
> them? For example, X-SVN may be used for git-svn.

Please don't.

When two people/programs create an otherwise identical (for the purpose of git) commits that have two different object names, there'd better be a very good reason other than "I felt like adding an extra header that I can use willy-nilly".

Please separate the 'note' part and the 'generation' part and make two separate discussion threads.

And kill 'note' part altogether, but that can be done in that thread ;-).