From: "Eric Bénard" <eric@eukrea.com>
To: openembedded-devel@lists.openembedded.org
Cc: koen@dominion.thruhere.net
Subject: Re: [meta-networking][PATCH] inetutils: fix compile error when PATH_PROCNET_DEV is undefined
Date: Wed, 18 Dec 2013 17:36:03 +0100 [thread overview]
Message-ID: <20131218173603.40ac0c16@e6520eb> (raw)
In-Reply-To: <l8sf7j$ksk$1@ger.gmane.org>
Hi Koen,
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/inetutils-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 ?
Eric
next prev parent reply other threads:[~2013-12-18 16:36 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 [this message]
2013-12-18 16:37 ` Koen Kooi
2013-12-18 16:42 ` Paul Eggleton
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=20131218173603.40ac0c16@e6520eb \
--to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox