From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] e2fsprogs: Rename the first patch to match the naming policy.
Date: Sat, 16 Nov 2013 02:02:39 +0100 [thread overview]
Message-ID: <5286C42F.3060802@mind.be> (raw)
In-Reply-To: <20131115104511.56ab9a97@skate>
On 15/11/13 10:45, Thomas Petazzoni wrote:
> Dear Thomas De Schampheleire,
>
> On Fri, 15 Nov 2013 10:39:52 +0100, Thomas De Schampheleire wrote:
>
>>> package/e2fsprogs/e2fsprogs-0001-sem-init-libs.patch | 11 +++++++++++
>>> package/e2fsprogs/e2fsprogs-sem-init-libs.patch | 11 -----------
>>> 2 files changed, 11 insertions(+), 11 deletions(-)
>>> create mode 100644 package/e2fsprogs/e2fsprogs-0001-sem-init-libs.patch
>>> delete mode 100644 package/e2fsprogs/e2fsprogs-sem-init-libs.patch
>>
>> Also here I wonder why git/git-format-patch did not recognize the move?
>
> Because you need to explicitly do a 'git format-patch -M', or configure
> Git in your ~/.gitconfig to enable rename detection permanently.
But anyway it doesn't really matter, since git-repack will convert it
into a proper rename. It just makes the patch on the list shorter and
easier to review.
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
next prev parent reply other threads:[~2013-11-16 1:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-15 9:30 [Buildroot] [PATCH] e2fsprogs: Rename the first patch to match the naming policy sonic.adi at gmail.com
2013-11-15 9:39 ` Thomas De Schampheleire
2013-11-15 9:45 ` Thomas Petazzoni
2013-11-16 1:02 ` Arnout Vandecappelle [this message]
2013-11-17 7:38 ` Peter Korsgaard
2013-12-25 11:42 ` 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=5286C42F.3060802@mind.be \
--to=arnout@mind.be \
--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