From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2 v2] package/libtirpc: bump version
Date: Sun, 14 Jun 2015 23:31:55 +0200 [thread overview]
Message-ID: <20150614233155.40f7b59d@free-electrons.com> (raw)
In-Reply-To: <09555f7a62006a5327be21dc3705ef6547c0a8c7.1434292018.git.yann.morin.1998@free.fr>
Dear Yann E. MORIN,
On Sun, 14 Jun 2015 16:29:05 +0200, Yann E. MORIN wrote:
> Bump to version 0.3.1:
> - update our patches
> - rename patches for proper numbering
> - drop patch 0007, applied upstream
It looks all good, but...
> -Subject: [PATCH] Disable parts of TIRPC requiring NIS support
> +Subject: [PATCH 1/5] Disable parts of TIRPC requiring NIS support
could you use "git format-patch -N" to avoid the numbering inside the
patches themselves? It generally quickly gets wrong when we add more
patches, and is a bit unnecessary due to the numbering already being
present through the file names.
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-06-14 21:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-14 14:29 [Buildroot] [PATCH 0/2 v2] package/libtirpc: bump and add new dependencies (branch yem/libtirpc) Yann E. MORIN
2015-06-14 14:29 ` [Buildroot] [PATCH 1/2 v2] package/libtirpc: bump version Yann E. MORIN
2015-06-14 21:31 ` Thomas Petazzoni [this message]
2015-06-14 14:29 ` [Buildroot] [PATCH 2/2 v2] package/libtirpc: does not build with musl libc Yann E. MORIN
2015-06-14 21:17 ` Thomas Petazzoni
2015-07-08 4:54 ` Jörg Krause
2015-07-08 7:31 ` 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=20150614233155.40f7b59d@free-electrons.com \
--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