git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Richard Quirk" <richard.quirk@gmail.com>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: git@vger.kernel.org
Subject: Re: git-cherry-pick no longer detecting moved files in 1.5.3.4
Date: Wed, 17 Oct 2007 09:55:13 +0200	[thread overview]
Message-ID: <cac9e4380710170055t3853979by9d12a9a2f989f9b9@mail.gmail.com> (raw)
In-Reply-To: <20071017073357.GA13801@spearce.org>

On 10/17/07, Shawn O. Pearce <spearce@spearce.org> wrote:
>
> That's an "old" bug.  Lars Hjemli fixed this in df3a02f612 back on
> Sept 25th.  You can get the fix from either Junio's or my git tree
> in the master branch.

Yes, with that fix setting the diff.renamelimit config value to 0
really does work. Thanks!

  reply	other threads:[~2007-10-17  7:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-16 22:17 git-cherry-pick no longer detecting moved files in 1.5.3.4 Richard Quirk
2007-10-16 22:35 ` Michele Ballabio
2007-10-17  7:18   ` Richard Quirk
2007-10-17  7:33     ` Shawn O. Pearce
2007-10-17  7:55       ` Richard Quirk [this message]
2007-10-17  0:58 ` 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=cac9e4380710170055t3853979by9d12a9a2f989f9b9@mail.gmail.com \
    --to=richard.quirk@gmail.com \
    --cc=git@vger.kernel.org \
    --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).