all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Kyle Meyer <kyle@kyleam.com>
Cc: clement.pitclaudel@live.com, schwab@linux-m68k.org,
	monnier@IRO.UMontreal.CA, 27953@debbugs.gnu.org
Subject: bug#27953: vc-region-history doesn't follow renames
Date: Sat, 05 Aug 2017 20:23:36 +0300	[thread overview]
Message-ID: <833796udwn.fsf@gnu.org> (raw)
In-Reply-To: <87poca9c7j.fsf@kyleam.com> (message from Kyle Meyer on Sat, 05 Aug 2017 13:05:52 -0400)

> From: Kyle Meyer <kyle@kyleam.com>
> Date: Sat, 05 Aug 2017 13:05:52 -0400
> Cc: Andreas Schwab <schwab@linux-m68k.org>,
> 	Stefan Monnier <monnier@IRO.UMontreal.CA>, 27953@debbugs.gnu.org
> 
> But you shouldn't need to add --follow here.  Renames should be followed
> by default when -L is used.  (At least, that's what I see using Git
> v2.13.3.)

I have 2.10 here, so maybe this was fixed later, but I don't see
renames followed when -L is used.  E.g., try this:

  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?





  reply	other threads:[~2017-08-05 17:23 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 [this message]
2017-08-05 18:03         ` Andreas Schwab
2017-08-05 18:26           ` Eli Zaretskii
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=833796udwn.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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.