From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 0/4] rt-tests: patches rename & versoin bump & support of non-NPTL tools
Date: Tue, 11 Nov 2014 21:59:04 +0100 [thread overview]
Message-ID: <87h9y5mp2f.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20141111161056.52d0cee7@free-electrons.com> (Thomas Petazzoni's message of "Tue, 11 Nov 2014 16:10:56 +0100")
>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:
Hi,
> I must confess that I don't actually don't know precisely how git
> encodes renames. But basically, my understanding is that even if you do
Easy, it doesn't. It just stores blobs and the old and new files will
share the same blob as they are identical. The rename detection is only
for how you want the commit to PRESENTED.
> "git mv", "git format-patch" will encode a rename as a complete removal
> + a complete addition, because that's the only way, in the traditional
> patch format, to express a rename. However, by passing -M to git
> format-patch, you tell git that it can generate a git patch, making the
> assumption that it's git that will be used to apply the patch, and not
> just the basic "patch" tool. In this case, it can encode the rename in
> a smarter way.
Indeed. You can enable it by default with something like:
git config --global diff.renames copy
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2014-11-11 20:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-10 9:59 [Buildroot] [PATCH 0/4] rt-tests: patches rename & versoin bump & support of non-NPTL tools Alexey Brodkin
2014-11-10 9:59 ` [Buildroot] [PATCH 1/4] rt-tests: rename patch to the new convention Alexey Brodkin
2014-11-10 9:59 ` [Buildroot] [PATCH 2/4] rt-tests: switch site from Debian snapshot to Linux's git Alexey Brodkin
2014-11-10 9:59 ` [Buildroot] [PATCH 3/4] rt-tests: bump version to 0.89 Alexey Brodkin
2014-11-10 9:59 ` [Buildroot] [PATCH 4/4] rt-tests: allow building subset of tests with non-NPTL toolchains Alexey Brodkin
2014-11-10 10:06 ` Thomas Petazzoni
2014-11-10 10:24 ` Alexey Brodkin
2014-11-11 14:43 ` [Buildroot] [PATCH 0/4] rt-tests: patches rename & versoin bump & support of non-NPTL tools Thomas Petazzoni
2014-11-11 15:01 ` Alexey Brodkin
2014-11-11 15:10 ` Thomas Petazzoni
2014-11-11 20:59 ` Peter Korsgaard [this message]
2014-11-11 22:15 ` Thomas Petazzoni
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=87h9y5mp2f.fsf@dell.be.48ers.dk \
--to=jacmet@uclibc.org \
--cc=buildroot@busybox.net \
/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