From: Grant Edwards <grant.b.edwards@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 8736] IPV6 forced on in busybox
Date: Thu, 3 Mar 2016 21:08:35 +0000 (UTC) [thread overview]
Message-ID: <nba94j$m0k$1@ger.gmane.org> (raw)
In-Reply-To: bug-8736-163-ImR2b9Yvou@https.bugs.busybox.net/
On 2016-03-03, bugzilla at busybox.net <bugzilla@busybox.net> wrote:
[Regarding restoring the ability to configure buildroot with IPv6
support disabled because some utilities don't work right with IPv6
enabled.]
> That sounds like a bug in busybox that should be fixed instead of
> worked around then. What exactly goes wrong? Have you reported the
> bug to the busybox developers?
I agree that IPv6 support (if broken) needs to be fixed. But I think
it's also important to restore the ability to disable IPv6 support. I
have customers who explicity state that they want no IPv6 support in
their products.
--
Grant Edwards grant.b.edwards Yow! Here I am in 53
at B.C. and all I want is a
gmail.com dill pickle!!
next prev parent reply other threads:[~2016-03-03 21:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-03 17:07 [Buildroot] [Bug 8736] New: IPV6 forced on in busybox bugzilla at busybox.net
2016-03-03 20:59 ` [Buildroot] [Bug 8736] " bugzilla at busybox.net
2016-03-03 21:08 ` Grant Edwards [this message]
2016-03-03 21:12 ` Peter Korsgaard
2016-03-03 21:15 ` Peter Korsgaard
2016-03-03 21:35 ` Grant Edwards
2016-03-03 21:05 ` bugzilla at busybox.net
2016-03-03 21:09 ` bugzilla at busybox.net
2016-03-03 21:13 ` bugzilla at busybox.net
2016-03-03 21:17 ` bugzilla at busybox.net
2016-03-03 21:43 ` bugzilla at busybox.net
2016-03-03 21:47 ` bugzilla at busybox.net
2016-03-03 22:33 ` bugzilla at busybox.net
2016-03-03 22:40 ` bugzilla at busybox.net
2016-03-04 16:10 ` bugzilla at busybox.net
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='nba94j$m0k$1@ger.gmane.org' \
--to=grant.b.edwards@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.