unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Philippe Vaucher <philippe.vaucher@gmail.com>
Cc: eric@ericabrahamsen.net, emacs-devel@gnu.org
Subject: Re: Emacs-diffs Digest, Vol 175, Issue 8
Date: Thu, 01 Jun 2017 20:44:21 +0300	[thread overview]
Message-ID: <83lgpbd2mi.fsf@gnu.org> (raw)
In-Reply-To: <CAGK7Mr7N6Fy=Ov2gjx_h6O8cyyQx7UWNEJLJEWACwQuqNuBFcQ@mail.gmail.com> (message from Philippe Vaucher on Thu, 1 Jun 2017 17:37:11 +0200)

> From: Philippe Vaucher <philippe.vaucher@gmail.com>
> Date: Thu, 1 Jun 2017 17:37:11 +0200
> Cc: Eric Abrahamsen <eric@ericabrahamsen.net>, Emacs developers <emacs-devel@gnu.org>
> 
>  Is this renaming really necessary? If it isn't, I'd prefer not to
>  rename, as doing so makes digging into history harder.
> 
> Hum, `git log` has `--follow` which works quite well and `git blame` tracks content changes anyway (not file
> names).
> The only "gotcha" when renaming a file is to avoid changing its contents as well, otherwise it makes detection
> more difficult.

Yes, some Git commands can follow renaming, but others cannot, at
least not easily.  For example, "git log -L" has problems when it
crosses the renaming.  I had more trouble with other commands, which I
cannot at the moment recall; at the very least one needs to use
unusual syntax or non-default options which are hard to remember, so
that gets in the way when you have the least time.

So renaming is okay if we really have to do that, but we shouldn't do
it just because we can.



      reply	other threads:[~2017-06-01 17:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.75394.1496303445.22740.emacs-diffs@gnu.org>
2017-06-01 14:26 ` Emacs-diffs Digest, Vol 175, Issue 8 Eli Zaretskii
2017-06-01 15:01   ` Eric Abrahamsen
2017-06-02  6:18     ` Eli Zaretskii
2017-06-02  8:56       ` Eric Abrahamsen
2017-06-01 15:37   ` Philippe Vaucher
2017-06-01 17:44     ` Eli Zaretskii [this message]

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=83lgpbd2mi.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=eric@ericabrahamsen.net \
    --cc=philippe.vaucher@gmail.com \
    /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).