From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: "Koen Kooi" <koen@dominion.thruhere.net>,
"Eric Bénard" <eric@eukrea.com>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-networking][PATCH] inetutils: fix compile error when PATH_PROCNET_DEV is undefined
Date: Wed, 18 Dec 2013 16:42:50 +0000 [thread overview]
Message-ID: <1921702.El3fv2RuWf@helios> (raw)
In-Reply-To: <2D278DF6-68CE-4D88-B356-E70750AE2FCC@dominion.thruhere.net>
On Wednesday 18 December 2013 17:37:24 Koen Kooi wrote:
> Op 18 dec. 2013, om 17:36 heeft Eric Bénard <eric@eukrea.com> het volgende
> geschreven:
> > Le Wed, 18 Dec 2013 16:33:24 +0100,
> > Koen Kooi <koen@dominion.thruhere.net> a écrit :
> >> Eric Bénard schreef op 18-12-13 16:20:
> >>> patch taken from :
> >>> http://repository.timesys.com/buildsources/i/inetutils/inetutils-1.9/ine
> >>> tutils-1.9-PATH_PROCNET_DEV.patch>>
> >> Put that in the patch itself please and also add an Upstream-Status tag.
> >
> > I don't know which status to put there as it's not upstream : which
> > one is appropriate ?
>
> I put in "Unknown" in that case, but that's not a valid option for OE-core
> recipes.
The valid list, as agreed by the TSC some time ago, is part of the document we
have here:
http://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
prev parent reply other threads:[~2013-12-18 16:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-18 15:20 [meta-networking][PATCH] inetutils: fix compile error when PATH_PROCNET_DEV is undefined Eric Bénard
2013-12-18 15:33 ` Koen Kooi
2013-12-18 16:36 ` Eric Bénard
2013-12-18 16:37 ` Koen Kooi
2013-12-18 16:42 ` Paul Eggleton [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=1921702.El3fv2RuWf@helios \
--to=paul.eggleton@linux.intel.com \
--cc=eric@eukrea.com \
--cc=koen@dominion.thruhere.net \
--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 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.