From: "Shawn O. Pearce" <spearce@spearce.org>
To: demerphq <demerphq@gmail.com>
Cc: Petr Baudis <pasky@suse.cz>, Nicolas Pitre <nico@fluxnic.net>,
git <git@vger.kernel.org>
Subject: Re: extra headers in commit objects
Date: Wed, 3 Feb 2010 12:31:48 -0800 [thread overview]
Message-ID: <20100203203148.GF14799@spearce.org> (raw)
In-Reply-To: <9b18b3111002031143h63aaa6bpa4c91d140a769bb0@mail.gmail.com>
demerphq <demerphq@gmail.com> wrote:
> On 3 February 2010 20:26, Petr Baudis <pasky@suse.cz> wrote:
> Right. The only solution i can see would have had to have been
> implemented already. And that would involved some headers being marked
> "pass through", some "marked throw away on cherry-pick" and some
> "choke horribly if you find this and dont know what it is".
>
> And even with somethng like that one wonders if notes arent really a
> better alternative to user defined headers anyway?
Yes, exactly.
I think notes turn out to be a much better way to store this extra
data, provided you are OK with them being disconnected during an
amend, cherry-pick, filter-branch, or rebase... :-)
And unlike additional headers, git implementations will likely
support notes, because they are a good way to attach additional
user data onto commits.
--
Shawn.
next prev parent reply other threads:[~2010-02-03 20:32 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-03 17:40 extra headers in commit objects Shawn O. Pearce
2010-02-03 18:15 ` Nicolas Pitre
2010-02-03 19:01 ` demerphq
2010-02-03 19:26 ` Shawn O. Pearce
2010-02-03 19:40 ` demerphq
2010-02-03 20:42 ` Junio C Hamano
2010-02-03 21:04 ` Shawn O. Pearce
2010-02-04 0:38 ` Junio C Hamano
2010-02-04 0:41 ` A Large Angry SCM
2010-02-03 19:26 ` Petr Baudis
2010-02-03 19:43 ` demerphq
2010-02-03 20:31 ` Shawn O. Pearce [this message]
2010-02-03 20:03 ` Nicolas Pitre
2010-02-03 19:53 ` Sverre Rabbelier
2010-02-03 19:58 ` Scott Chacon
2010-02-03 22:48 ` Shawn O. Pearce
2010-02-04 6:24 ` Mike Hommey
2010-02-03 20:58 ` Jelmer Vernooij
2010-02-03 21:17 ` Nicolas Pitre
2010-02-03 22:39 ` Shawn O. Pearce
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=20100203203148.GF14799@spearce.org \
--to=spearce@spearce.org \
--cc=demerphq@gmail.com \
--cc=git@vger.kernel.org \
--cc=nico@fluxnic.net \
--cc=pasky@suse.cz \
/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).