From: "Eckhard Maaß" <eckhard.s.maass@googlemail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Jeff King <peff@peff.net>, Bryan Turner <bturner@atlassian.com>,
dylanyoungmeijer@gmail.com, Git Users <git@vger.kernel.org>
Subject: Re: [Possible GIT Bug]
Date: Mon, 10 Sep 2018 19:35:12 +0200 [thread overview]
Message-ID: <20180910173512.GA22152@esm> (raw)
In-Reply-To: <xmqqin3duypt.fsf@gitster-ct.c.googlers.com>
On Mon, Sep 10, 2018 at 09:03:10AM -0700, Junio C Hamano wrote:
> It is neither but if I have to pick one between the two, it is much
> closer to the former than the latter. The primary source of this is
> that we have only *one* pathspec given to the diff machinery, but in
> order to implement your ideal "find harder", you'd need *two*. That
> is, one set of paths for which you are interested in their origin,
> and the other set that you allow the machinery to consider as possible
> origins. Since we can only give one pathspec machinery, that one
> pathspec is used to specify both of these sets.
How does tihs compare to `--follow`? With that knob active the machinery
indeed uses the whole repository for finding renames and/or copies. Is
this the only exception then?
Take care,
Eckhard
next prev parent reply other threads:[~2018-09-10 17:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAPGJNu5RPXjeib-vayVzmFkU9cZ=h5o5VDoM1vQqv2+HgtNXLw@mail.gmail.com>
2018-09-09 13:30 ` Fwd: [Possible GIT Bug] Dylan Young
2018-09-09 19:04 ` Bryan Turner
2018-09-10 13:24 ` Jeff King
2018-09-10 16:03 ` Junio C Hamano
2018-09-10 17:35 ` Eckhard Maaß [this message]
2018-09-10 18:37 ` 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=20180910173512.GA22152@esm \
--to=eckhard.s.maass@googlemail.com \
--cc=bturner@atlassian.com \
--cc=dylanyoungmeijer@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.net \
/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).