All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 813] New: Drop not very useful generic package selection options (access point, firewall, dev system)
Date: Mon, 14 Dec 2009 20:36:24 +0000 (UTC)	[thread overview]
Message-ID: <bug-813-163@https.bugs.busybox.net/> (raw)

https://bugs.busybox.net/show_bug.cgi?id=813

           Summary: Drop not very useful generic package selection options
                    (access point, firewall, dev system)
           Product: buildroot
           Version: unspecified
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: trivial
          Priority: P5
         Component: Other
        AssignedTo: unassigned at buildroot.uclibc.org
        ReportedBy: gustavo at zacarias.com.ar
                CC: buildroot at uclibc.org
   Estimated Hours: 0.0


Created an attachment (id=843)
 --> (https://bugs.busybox.net/attachment.cgi?id=843)
Drop generic package selection options

Don't think they're too useful or used generally.
They're open to multiple interpretations so people could ask for more/less
packages to suit their needs and new options for other things (like generic
access point, generic NAS, so on...) without a clear definition of which
packages would be required/the bare minimum for them.


-- 
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.

             reply	other threads:[~2009-12-14 20:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-14 20:36 bugzilla at busybox.net [this message]
2009-12-26  8:14 ` [Buildroot] [Bug 813] Drop not very useful generic package selection options (access point, firewall, dev system) 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-813-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.