From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] libcap: rename existing patch
Date: Sat, 2 Nov 2013 19:36:47 +0100 [thread overview]
Message-ID: <20131102193647.159dd73d@skate> (raw)
In-Reply-To: <1383328047-28945-1-git-send-email-thomas.petazzoni@free-electrons.com>
Dear Thomas Petazzoni,
On Fri, 1 Nov 2013 18:47:26 +0100, Thomas Petazzoni wrote:
> libcap currently has one patch, but it is named using the old naming
> strategy, which includes the package version, but not a patch
> number. This commit switches this to use the new patch naming
> strategy.
>
> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
> ---
> .../{libcap-2.22-build-system.patch => libcap-01-build-system.patch} | 0
> 1 file changed, 0 insertions(+), 0 deletions(-)
> rename package/libcap/{libcap-2.22-build-system.patch => libcap-01-build-system.patch} (100%)
>
> diff --git a/package/libcap/libcap-2.22-build-system.patch b/package/libcap/libcap-01-build-system.patch
> similarity index 100%
> rename from package/libcap/libcap-2.22-build-system.patch
> rename to package/libcap/libcap-01-build-system.patch
Committed both patches to for-peter-2013.11, thanks.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2013-11-02 18:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-01 17:47 [Buildroot] [PATCH 1/2] libcap: rename existing patch Thomas Petazzoni
2013-11-01 17:47 ` [Buildroot] [PATCH 2/2] libcap: fix static link Thomas Petazzoni
2013-11-02 17:59 ` Samuel Martin
2013-11-02 18:01 ` Yann E. MORIN
2013-11-04 21:08 ` Peter Korsgaard
2013-11-02 17:55 ` [Buildroot] [PATCH 1/2] libcap: rename existing patch Yann E. MORIN
2013-11-02 18:01 ` Samuel Martin
2013-11-02 18:36 ` Thomas Petazzoni [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20131102193647.159dd73d@skate \
--to=thomas.petazzoni@free-electrons.com \
--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