From: "Nguyen Thai Ngoc Duy" <pclouds@gmail.com>
To: "Daniel Barkalow" <barkalow@iabervon.org>
Cc: "Jakub Narebski" <jnareb@gmail.com>, git@vger.kernel.org
Subject: Re: [RFC] New commit object headers: generation and note headers
Date: Sun, 10 Feb 2008 00:50:12 +0700 [thread overview]
Message-ID: <fcaeb9bf0802090950l27aa247ei5d067e0f24fcade0@mail.gmail.com> (raw)
In-Reply-To: <alpine.LNX.1.00.0802091220030.13593@iabervon.org>
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.
--
Duy
next prev parent reply other threads:[~2008-02-09 17:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-09 16:46 [RFC] New commit object headers: generation and note headers Jakub Narebski
2008-02-09 17:35 ` Daniel Barkalow
2008-02-09 17:50 ` Nguyen Thai Ngoc Duy [this message]
2008-02-09 21:03 ` Junio C Hamano
2008-02-09 23:26 ` [RFC] New commit object headers: " Jakub Narebski
2008-02-10 1:08 ` Johannes Schindelin
2008-02-11 10:08 ` Jakub Narebski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=fcaeb9bf0802090950l27aa247ei5d067e0f24fcade0@mail.gmail.com \
--to=pclouds@gmail.com \
--cc=barkalow@iabervon.org \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).