Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 3985] New: "help" target's defconfig list needs sort
Date: Sun, 17 Jul 2011 02:07:09 +0000 (UTC)	[thread overview]
Message-ID: <bug-3985-163@https.bugs.busybox.net/> (raw)

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

           Summary: "help" target's defconfig list needs sort
           Product: buildroot
           Version: unspecified
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: trivial
          Priority: P5
         Component: Other
        AssignedTo: unassigned at buildroot.uclibc.org
        ReportedBy: d_mo1234 at yahoo.com
                CC: buildroot at uclibc.org
   Estimated Hours: 0.0


Created attachment 3481
  --> https://bugs.busybox.net/attachment.cgi?id=3481
patch file to add sort to "help" target's defconfig list

The latest "make" version, 3.82, changed the behavior of "wildcard" to no
longer sort its output.  The result is that the defconfig list in buildroot's
"help" target now lists things in some bizarro order.  Not good for those of us
who manage multiple configurations.  It would help if a "sort" were added.  A
patch is attached.

-- 
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:[~2011-07-17  2:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-17  2:07 bugzilla at busybox.net [this message]
2011-07-17 20:19 ` [Buildroot] [Bug 3985] "help" target's defconfig list needs sort 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-3985-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox