git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff King <peff@peff.net>
To: "Pierre Habouzit" <madcoder@debian.org>,
	"Junio C Hamano" <gitster@pobox.com>,
	sverre@rabbelier.nl, "Björn Steinbrink" <B.Steinbrink@gmx.de>,
	"Stephen R. van den Berg" <srb@c>
Subject: Re: git blame not respecting --find-copies-harder ?
Date: Thu, 31 Jul 2008 05:05:28 -0400	[thread overview]
Message-ID: <20080731090528.GC20691@sigill.intra.peff.net> (raw)
In-Reply-To: <20080731090146.GA12867@artemis.madism.org>

On Thu, Jul 31, 2008 at 11:01:46AM +0200, Pierre Habouzit wrote:

>   Ack this is a correct fix. I wonder how this even works with other
> commands that use --all and stuff like that.

--all is parsed separately in setup_revisions _before_ we call
handle_revision_opt. So the only codepath hitting that is parse_options
users who call parse_revision_opt (i.e., blame and shortlog).

-Peff

  reply	other threads:[~2008-07-31  9:06 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-30  9:39 git blame not respecting --find-copies-harder ? Stephen R. van den Berg
2008-07-30 15:01 ` Björn Steinbrink
2008-07-30 15:43   ` Sverre Rabbelier
2008-07-31  6:48     ` Jeff King
2008-07-31  7:05       ` Junio C Hamano
2008-07-31  7:21         ` Jeff King
2008-07-31  7:36           ` Junio C Hamano
2008-07-31  8:25             ` Jeff King
2008-07-31  8:35               ` Junio C Hamano
2008-07-31  9:01                 ` Pierre Habouzit
2008-07-31  9:05                   ` Jeff King [this message]
2008-07-31  9:06                   ` Pierre Habouzit
2008-07-31  9:03                 ` Jeff King
2008-07-31  9:15                   ` Pierre Habouzit
2008-07-31  9:34                     ` Jeff King
2008-07-31 10:22                       ` Pierre Habouzit
2008-07-31 10:33                         ` Jeff King

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=20080731090528.GC20691@sigill.intra.peff.net \
    --to=peff@peff.net \
    --cc=B.Steinbrink@gmx.de \
    --cc=gitster@pobox.com \
    --cc=madcoder@debian.org \
    --cc=srb@c \
    --cc=sverre@rabbelier.nl \
    /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).