From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] igmpproxy: new package
Date: Thu, 12 Sep 2013 23:44:06 +0200 [thread overview]
Message-ID: <87ob7xpvfd.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <1379018757-27111-1-git-send-email-mlweber1@rockwellcollins.com> (Matt Weber's message of "Thu, 12 Sep 2013 15:45:57 -0500")
>>>>> "Matt" == Matt Weber <mlweber1@rockwellcollins.com> writes:
Matt> Signed-off-by: Matt Weber <mlweber1@rockwellcollins.com>
Committed with minor white space fixes, thanks.
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2013-09-12 21:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-12 20:45 [Buildroot] [PATCH v2] igmpproxy: new package Matt Weber
2013-09-12 21:44 ` Peter Korsgaard [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=87ob7xpvfd.fsf@dell.be.48ers.dk \
--to=jacmet@uclibc.org \
--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