From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] Updating /etc/protocols
Date: Sat, 26 Oct 2013 08:55:13 +0200 [thread overview]
Message-ID: <87iowk4j3i.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <CANGB_5aKYOo2hH+t5yGG5-34-uBNiLHnNHh5Ur_LEAPYEomq-A@mail.gmail.com> (Peter Sanford's message of "Fri, 25 Oct 2013 17:19:37 -0700")
>>>>> "Peter" == Peter Sanford <psanford@nearbuysystems.com> writes:
> Yeah that was basically why I was asking. I also wanted to verify
> that there wasn't any licencing reasons for using a BSD source
> originally. ?If that's the case I will probably just grab the Debian
> version[1] which is quite a bit more concise than the NetBSD one.
Sounds good, please do.
Thanks.
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2013-10-26 6:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-25 23:50 [Buildroot] Updating /etc/protocols Peter Sanford
2013-10-26 0:02 ` Gustavo Zacarias
2013-10-26 0:19 ` Peter Sanford
2013-10-26 6:55 ` 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=87iowk4j3i.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