From: Eli Zaretskii <eliz@gnu.org>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: clement.pitclaudel@live.com, kyle@kyleam.com,
monnier@IRO.UMontreal.CA, 27953@debbugs.gnu.org
Subject: bug#27953: vc-region-history doesn't follow renames
Date: Sat, 05 Aug 2017 21:26:53 +0300 [thread overview]
Message-ID: <83zibduaz6.fsf@gnu.org> (raw)
In-Reply-To: <874ltlj3j0.fsf@linux-m68k.org> (message from Andreas Schwab on Sat, 05 Aug 2017 20:03:15 +0200)
> From: Andreas Schwab <schwab@linux-m68k.org>
> Cc: Kyle Meyer <kyle@kyleam.com>, clement.pitclaudel@live.com, monnier@IRO.UMontreal.CA, 27953@debbugs.gnu.org
> Date: Sat, 05 Aug 2017 20:03:15 +0200
>
> > git log -L77,83:admin/charsets/Makefile.in
> >
> > You will see Git claiming the only version which changed that is the
> > one in which Makefile.in was created from Makefile. Am I doing
> > something wrong, or expecting too much?
>
> The problem is that admin/charsets/Makefile.in is only similar to
> admin/charsets/Makefile by 32%, much below the default threshold.
They look very similar to me...
What about doc/emacs/Makefile.in? That should be almost 100% similar
to its origin in man/Makefile.in, when it was moved from there, but
"git -L" still cannot cross the boundary.
next prev parent reply other threads:[~2017-08-05 18:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-04 15:12 bug#27953: vc-region-history doesn't follow renames Clément Pit--Claudel
2017-08-04 17:21 ` Stefan Monnier
2017-08-04 17:40 ` Andreas Schwab
2017-08-05 13:06 ` Clément Pit--Claudel
2017-08-05 17:05 ` Kyle Meyer
2017-08-05 17:23 ` Eli Zaretskii
2017-08-05 18:03 ` Andreas Schwab
2017-08-05 18:26 ` Eli Zaretskii [this message]
2017-08-05 20:06 ` Kyle Meyer
2017-08-05 17:27 ` Clément Pit--Claudel
2017-08-05 20:55 ` Kyle Meyer
2017-08-05 18:08 ` Andreas Schwab
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83zibduaz6.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=27953@debbugs.gnu.org \
--cc=clement.pitclaudel@live.com \
--cc=kyle@kyleam.com \
--cc=monnier@IRO.UMontreal.CA \
--cc=schwab@linux-m68k.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).