From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] new network package - open-lldp
Date: Fri, 12 Jan 2018 10:51:28 +0100 [thread overview]
Message-ID: <20180112105128.298b0006@windsurf.lan> (raw)
In-Reply-To: <908739567.1360235.1515749250544@mail.yahoo.com>
Hello Laurent,
On Fri, 12 Jan 2018 09:27:30 +0000 (UTC), Laurent Charpentier wrote:
> I would like to add the open-lldp (lldpad daemon) package to buildroot.
> I attached the patch file
> 0001-Added-lldpad-LLDP-Agent-Daemon-package.patch
Thanks for your contribution! As explained in our manual at
https://buildroot.org/downloads/manual/manual.html#submitting-patches,
we would like patches to be sent inline (preferably using git
send-email), so that we can do a reply to review the patch.
Could you use git send-email to resend your patch ?
Thanks a lot!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
prev parent reply other threads:[~2018-01-12 9:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <908739567.1360235.1515749250544.ref@mail.yahoo.com>
2018-01-12 9:27 ` [Buildroot] new network package - open-lldp Laurent Charpentier
2018-01-12 9:51 ` Thomas Petazzoni [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=20180112105128.298b0006@windsurf.lan \
--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