From: Andreas Schwab <schwab@linux-m68k.org>
To: Glenn Morris <rgm@gnu.org>
Cc: Emacs developers <emacs-devel@gnu.org>
Subject: Re: master updated (8244357 -> 41f91d3)
Date: Thu, 02 Mar 2017 10:02:28 +0100 [thread overview]
Message-ID: <87tw7cvyor.fsf@linux-m68k.org> (raw)
In-Reply-To: <mjvarsa1xn.fsf@fencepost.gnu.org> (Glenn Morris's message of "Wed, 01 Mar 2017 20:43:16 -0500")
On Mär 01 2017, Glenn Morris <rgm@gnu.org> wrote:
>> Summary of changes:
> [...]
>> test/{src/alloc-tests.el => lisp/net/puny.el} | 32 +++++++++++++++++--------
> [...]
>> copy test/{src/alloc-tests.el => lisp/net/puny.el} (51%)
>
> Say whaat?
> I guess this is what happens when your VCS doesn't do proper rename
> tracking, and you have small files where the identical license
> boilerplate makes up a large fraction of the content?
That's the difference between rename detection and copy detection:
$ git diff -M --stat --summary 8244357 41f91d3
lisp/net/puny.el | 10 ++++++----
test/lisp/net/puny.el | 41 +++++++++++++++++++++++++++++++++++++++++
2 files changed, 47 insertions(+), 4 deletions(-)
create mode 100644 test/lisp/net/puny.el
$ git diff -C --stat --summary 8244357 41f91d3
lisp/net/puny.el | 10 +++++----
test/{src/alloc-tests.el => lisp/net/puny.el} | 32 +++++++++++++++++----------
2 files changed, 26 insertions(+), 16 deletions(-)
copy test/{src/alloc-tests.el => lisp/net/puny.el} (51%)
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
prev parent reply other threads:[~2017-03-02 9:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20170302013628.1001.55742@vcs0.savannah.gnu.org>
2017-03-02 1:43 ` master updated (8244357 -> 41f91d3) Glenn Morris
2017-03-02 1:51 ` Lars Ingebrigtsen
2017-03-02 2:07 ` Glenn Morris
2017-03-02 9:02 ` Andreas Schwab [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=87tw7cvyor.fsf@linux-m68k.org \
--to=schwab@linux-m68k.org \
--cc=emacs-devel@gnu.org \
--cc=rgm@gnu.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).