From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 5066] New: New-Package: net-tools
Date: Wed, 11 Apr 2012 07:56:45 +0000 (UTC) [thread overview]
Message-ID: <bug-5066-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=5066
Summary: New-Package: net-tools
Product: buildroot
Version: unspecified
Platform: PC
OS/Version: All
Status: NEW
Severity: enhancement
Priority: P5
Component: Other
AssignedTo: unassigned at buildroot.uclibc.org
ReportedBy: tech at davengo.com
CC: buildroot at uclibc.org
Estimated Hours: 0.0
Created attachment 4256
--> https://bugs.busybox.net/attachment.cgi?id=4256
Patch
Added a package for "The NET-3 networking toolkit".
Adding arp, ifconfig, netstat, rarp, nameif and route to the target system.
Build tested on i686 architecture.
Best regards,
Stefan Mei?ner, davengo GmbH, Germany
--
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next reply other threads:[~2012-04-11 7:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-11 7:56 bugzilla at busybox.net [this message]
2013-12-11 17:12 ` [Buildroot] [Bug 5066] New-Package: net-tools 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=bug-5066-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--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.