From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] iproute2: bump to version 4.14.1
Date: Wed, 15 Nov 2017 15:08:34 +0100 [thread overview]
Message-ID: <87o9o3ljml.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20171115092154.wkmktmstb5i7ujwc@sapphire.tkos.co.il> (Baruch Siach's message of "Wed, 15 Nov 2017 11:21:55 +0200")
>>>>> "Baruch" == Baruch Siach <baruch@tkos.co.il> writes:
Hi,
>> I see that you didn't mark this as being for next. Is that on purpose?
>> If so, why?
> No purpose. I just thought it's obvious.
> Would you prefer to have all patches for next marked in the subject prefix
> during the -rc period?
It is always nice to be explicit, but it isn't a big deal. I just
wondered as you used next in the patch just before, but not here:
[ 96: Baruch Siach ] [PATCH next v2 1/2] gnupg2: don't preserve the old gpg2 executable name [9.7k]
[ 239: Baruch Siach ] [PATCH] iproute2: bump to version 4.14.1 [14k]
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2017-11-15 14:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-14 18:27 [Buildroot] [PATCH] iproute2: bump to version 4.14.1 Baruch Siach
2017-11-15 9:17 ` Peter Korsgaard
2017-11-15 9:21 ` Baruch Siach
2017-11-15 14:08 ` Peter Korsgaard [this message]
2017-11-15 21:12 ` 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=87o9o3ljml.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.