From: Mike Hommey <mh@glandium.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: Should notes handle replace commits?
Date: Sat, 9 Jan 2016 10:25:42 +0900 [thread overview]
Message-ID: <20160109012542.GA2445@glandium.org> (raw)
In-Reply-To: <xmqqmvsfzhq4.fsf@gitster.mtv.corp.google.com>
On Fri, Jan 08, 2016 at 05:04:03PM -0800, Junio C Hamano wrote:
> It is not graft vs replace. It is about what you replace with what
> other thing: "replace" is a content replacement mechanism, not
> identity replacement mechanism.
I guess this is where opinions diverge: in what notes are.
I'd argue notes are content just as much as the tree, except they're not
stored inside the commit.
Mike
next prev parent reply other threads:[~2016-01-09 1:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-08 1:28 Should notes handle replace commits? Mike Hommey
2016-01-08 20:09 ` Junio C Hamano
2016-01-08 21:49 ` Mike Hommey
2016-01-08 23:51 ` Junio C Hamano
2016-01-09 0:13 ` Junio C Hamano
2016-01-09 0:32 ` Mike Hommey
2016-01-09 0:25 ` Mike Hommey
2016-01-09 1:04 ` Junio C Hamano
2016-01-09 1:25 ` Mike Hommey [this message]
2016-01-11 16:09 ` Junio C Hamano
2016-01-09 17:39 ` Philip Oakley
2016-01-11 16:50 ` Junio C Hamano
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=20160109012542.GA2445@glandium.org \
--to=mh@glandium.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).