From: bugs at busybox.net <bugs@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [buildroot 0000095]: make menuconfig does not work.
Date: Mon, 12 Feb 2007 05:51:11 -0800 [thread overview]
Message-ID: <6b1b1691b345f18a3cfd84480d720de4@bugs.busybox.net> (raw)
The following issue has been ASSIGNED.
======================================================================
http://busybox.net/bugs/view.php?id=95
======================================================================
Reported By: thomasez
Assigned To: buildroot
======================================================================
Project: buildroot
Issue ID: 95
Category: Architecture Specific
Reproducibility: always
Severity: minor
Priority: normal
Status: assigned
======================================================================
Date Submitted: 02-10-2005 13:53 PST
Last Modified: 02-12-2007 05:51 PST
======================================================================
Summary: make menuconfig does not work.
Description:
After the switch to svn, something might have been forgotten:
next reply other threads:[~2007-02-12 13:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-12 13:51 bugs at busybox.net [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-03-08 8:13 [Buildroot] [buildroot 0000095]: make menuconfig does not work bugs 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=6b1b1691b345f18a3cfd84480d720de4@bugs.busybox.net \
--to=bugs@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