git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: Michael Haggerty <mhagger@alum.mit.edu>,
	Christian Couder <christian.couder@gmail.com>,
	git@vger.kernel.org
Subject: Re: [PATCH] disable grafts during fetch/push/bundle
Date: Thu, 6 Mar 2014 14:07:57 -0500	[thread overview]
Message-ID: <20140306190757.GA27583@sigill.intra.peff.net> (raw)
In-Reply-To: <xmqqbnxjywxz.fsf@gitster.dls.corp.google.com>

On Thu, Mar 06, 2014 at 11:00:08AM -0800, Junio C Hamano wrote:

> Jeff King <peff@peff.net> writes:
> 
> > I also noticed that the diff engine does not play well with replacements
> > of blobs. When we are diffing the trees, we see that the sha1 for path
> > "foo" is the same on either side, and do not look further, even though
> > feeding those sha1s to builtin_diff would fetch the replacements.
> 
> Sorry, I do not quite understand.
> 
> In "git diff A B -- path", if the object name recorded for A:path
> and B:path are the same, but the replacement mechanism maps the
> object name for that blob object to some other blob object, wouldn't
> the result be empty because both sides replace to the same thing
> anyway?

Oh, right, I was being stupid. I did:

  git replace --edit HEAD:some-file

and expected "git show" to find the diff. But that doesn't make sense.
On top of that, I need to do:

  git replace --edit HEAD^{tree}

to replace the sha1 of the entry in the tree. In which case diff would
find it just fine.

-Peff

  reply	other threads:[~2014-03-06 19:08 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-04 17:48 [PATCH] disable grafts during fetch/push/bundle Jeff King
2014-03-04 20:52 ` Junio C Hamano
2014-03-05  0:56   ` Jeff King
2014-03-05 18:49     ` Junio C Hamano
2014-03-05 18:52       ` Jeff King
2014-03-05 19:18         ` Junio C Hamano
2014-03-05 19:28           ` Jeff King
2014-03-05 20:24             ` Junio C Hamano
2014-03-06  8:42           ` Michael Haggerty
2014-03-06  9:17             ` Christian Couder
2014-03-06 15:56             ` Jeff King
2014-03-06 16:41               ` Michael Haggerty
2014-03-06 17:48                 ` Jeff King
2014-03-06 17:49                   ` [RFC/PATCH 1/4] replace: refactor command-mode determination Jeff King
2014-03-06 17:49                   ` [RFC/PATCH 2/4] replace: use OPT_CMDMODE to handle modes Jeff King
     [not found]                     ` <CAP8UFD2c0UKT8Uyw4j9SzKGx2oLn=o7N-dtvQHPaaBtLT6ggcw@mail.gmail.com>
2014-03-06 18:48                       ` Jeff King
2014-03-06 17:49                   ` [RFC/PATCH 3/4] replace: factor object resolution out of replace_object Jeff King
2014-03-06 17:51                   ` [RFC/PATCH 4/4] replace: add --edit option Jeff King
2014-03-07  1:57                     ` Eric Sunshine
2014-03-07 17:17                       ` Jeff King
2014-03-06 19:00                   ` [PATCH] disable grafts during fetch/push/bundle Junio C Hamano
2014-03-06 19:07                     ` Jeff King [this message]
2014-03-06 23:01                   ` Philip Oakley
2014-03-06 23:29                     ` Michael Haggerty
2014-03-06 23:39                       ` Junio C Hamano
2014-03-07  7:08                         ` Christian Couder
2014-03-07 17:19                           ` Jeff King
2014-03-19 22:39                             ` Junio C Hamano
2014-03-21  0:49                               ` Jeff King
2014-03-06 23:48                       ` Philip Oakley
2014-03-04 23:36 ` Eric Sunshine
2014-03-05  0:37   ` Jeff King
2014-03-05  1:00     ` Eric Sunshine
2014-03-05  1:05       ` Jeff King
2014-03-05  1:07         ` Eric Sunshine

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=20140306190757.GA27583@sigill.intra.peff.net \
    --to=peff@peff.net \
    --cc=christian.couder@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=mhagger@alum.mit.edu \
    /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).