From: Joe MacDonald <Joe.MacDonald@windriver.com>
To: <openembedded-devel@lists.openembedded.org>
Subject: Re: [meta-networking][PATCH] ipsec-tools: update Upstream-Status for patch
Date: Wed, 19 Jun 2013 10:17:53 -0400 [thread overview]
Message-ID: <20130619141753.GA8093@windriver.com> (raw)
In-Reply-To: <1371598570-16322-1-git-send-email-paul@paulbarker.me.uk>
[-- Attachment #1: Type: text/plain, Size: 608 bytes --]
[[oe] [meta-networking][PATCH] ipsec-tools: update Upstream-Status for patch] On 13.06.19 (Wed 00:36) Paul Barker wrote:
> I've not seen anyone else send in a patch just to change Upstream-Status so this
> may be unnecessary churn. Let me know if it is.
I'm happy to have the update. It's nice to have the loop closed in this
way. Thanks Paul.
-J.
>
> Paul Barker (1):
> ipsec-tools: update Upstream-Status for patch
>
> .../ipsec-tools/ipsec-tools/0001-Fix-warning-with-gcc-4.8.patch | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
--
-Joe MacDonald.
:wq
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]
prev parent reply other threads:[~2013-06-19 14:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-18 23:36 [meta-networking][PATCH] ipsec-tools: update Upstream-Status for patch Paul Barker
2013-06-18 23:36 ` Paul Barker
2013-06-19 14:17 ` Joe MacDonald [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=20130619141753.GA8093@windriver.com \
--to=joe.macdonald@windriver.com \
--cc=openembedded-devel@lists.openembedded.org \
/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