From: Mike Hommey <mh@glandium.org>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: Scott Chacon <schacon@gmail.com>, git <git@vger.kernel.org>
Subject: Re: extra headers in commit objects
Date: Thu, 4 Feb 2010 07:24:49 +0100 [thread overview]
Message-ID: <20100204062449.GC6097@glandium.org> (raw)
In-Reply-To: <20100203224835.GK14799@spearce.org>
On Wed, Feb 03, 2010 at 02:48:35PM -0800, Shawn O. Pearce wrote:
> > Anyhow, I was saying that _technically_ you can artificially write
> > extra headers into the commit object (though at the time Dulwich
> > didn't support reading them because of how it parsed commit objects -
> > I believe it would actually explode if it saw something it didn't
> > expect). I said I was still going to keep the metadata in my
> > implementation in the message, but he was very interested in hiding
> > his in the commit headers.
>
> Yea, everyone wants to hide that extra metadata. I never get why.
> Even in SVN. Why wouldn't I want to see the bug(s) fixed by
> a commit? Difference of opinion. I also happen to prefer the
> color blue. Dammit, everyone should prefer blue.
Note, though, that such information may change in the future, in which
case you can't rewrite the commit to fit that.
But for all that, there are git-notes, now, aren't there ?
Mike
next prev parent reply other threads:[~2010-02-04 6:25 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
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 [this message]
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=20100204062449.GC6097@glandium.org \
--to=mh@glandium.org \
--cc=git@vger.kernel.org \
--cc=schacon@gmail.com \
--cc=spearce@spearce.org \
/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).