From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 4/7] portmap: add nommu support
Date: Tue, 11 Jan 2011 21:30:19 +0100 [thread overview]
Message-ID: <87tyhfyyhw.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <201101111250.24179.vapier@gentoo.org> (Mike Frysinger's message of "Tue, 11 Jan 2011 12:50:23 -0500")
>>>>> "Mike" == Mike Frysinger <vapier@gentoo.org> writes:
Hi,
Mike> On Tuesday, January 11, 2011 05:29:45 Peter Korsgaard wrote:
>> What's the upstream status of these patches?
Mike> they've been sent multiple times, but upstream portmap hasnt
Mike> responded to anyone in a while
Ok, thanks.
>> What is this NO_PERROR thing? That belongs in the next patch rather than
>> here, right?
Mike> yes
Ok.
>> Why not simply rename it like the recent issue with getline -> get_line
>> in kconfig?
Mike> because perror is a standard, not a gnuism like getline
Yes, but why is there a perror() implementation in portmapper in the
first place? It seems like they want
something-looking-like-perror-but-using-syslog, rather than the real
perror?
>> Out of interest, what functionaly in portmapper do you miss with
>> NO_FORK?
Mike> the forks are only used to speed up responses
Ok.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2011-01-11 20:30 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-10 14:28 [Buildroot] Pull request buildroot.git (vapier branch) Mike Frysinger
2011-01-10 14:28 ` [Buildroot] [PATCH 1/7] busybox: unify duplicated build steps Mike Frysinger
2011-01-10 14:28 ` [Buildroot] [PATCH 2/7] busybox: let buildroot handle stripping Mike Frysinger
2011-01-11 9:52 ` Peter Korsgaard
2011-01-10 14:28 ` [Buildroot] [PATCH 3/7] toolchain: add a USE_MMU build option Mike Frysinger
2011-01-14 12:29 ` Peter Korsgaard
2011-01-14 21:27 ` Mike Frysinger
2011-01-14 21:53 ` Peter Korsgaard
2011-01-14 22:17 ` Mike Frysinger
2011-01-15 13:25 ` Peter Korsgaard
2011-01-10 14:28 ` [Buildroot] [PATCH 4/7] portmap: add nommu support Mike Frysinger
2011-01-11 10:29 ` Peter Korsgaard
2011-01-11 17:50 ` Mike Frysinger
2011-01-11 20:30 ` Peter Korsgaard [this message]
2011-01-16 1:20 ` Mike Frysinger
2011-01-11 18:00 ` [Buildroot] [PATCH 4/7 v2] " Mike Frysinger
2011-01-19 21:19 ` Peter Korsgaard
2011-01-10 14:28 ` [Buildroot] [PATCH 5/7] portmap: respect target CFLAGS Mike Frysinger
2011-01-19 21:20 ` Peter Korsgaard
2011-01-10 14:28 ` [Buildroot] [PATCH 6/7] portmap: fix clean target to actually clean Mike Frysinger
2011-01-19 21:21 ` Peter Korsgaard
2011-01-10 14:28 ` [Buildroot] [PATCH 7/7] tcpdump: add patch for nommu systems Mike Frysinger
2011-01-19 21:52 ` Peter Korsgaard
2011-01-11 9:52 ` [Buildroot] [PATCH 1/7] busybox: unify duplicated build steps Peter Korsgaard
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=87tyhfyyhw.fsf@macbook.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