From: "James H. Cloos Jr." <cloos@jhcloos.com>
To: linux-kernel@vger.kernel.org
Subject: Re: make help ARCH=xx fun
Date: Sun, 22 Feb 2004 09:28:04 -0500 [thread overview]
Message-ID: <m3ishzqjd7.fsf@lugabout.jhcloos.org> (raw)
In-Reply-To: <20040222095021.GB2266@mars.ravnborg.org> (Sam Ravnborg's message of "Sun, 22 Feb 2004 10:50:21 +0100")
>>>>> "Sam" == Sam Ravnborg <sam@ravnborg.org> writes:
Sam> The sh people have decided to create the list based on the
Sam> content of the directory. Therefore you see the SCCS entry,
I thought that went w/o saying....
The points were that if doing a readdir(3) in the tree for config
files, it would not be a bad idea to ignore directories and that
each arch should have arch-specific make help support (the cited
example was that ppc64 lacked it even though ppc had some).
-JimC
next prev parent reply other threads:[~2004-02-22 14:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-21 14:26 James H. Cloos Jr.
2004-02-22 9:50 ` Sam Ravnborg
2004-02-22 14:28 ` James H. Cloos Jr. [this message]
2004-02-24 21:55 ` Tom Rini
2004-02-25 19:00 ` Sam Ravnborg
2004-02-25 18:08 ` Tom Rini
2004-02-25 18:30 ` Paul Mundt
2004-02-25 18:39 ` Tom Rini
2004-02-25 18:44 ` Paul Mundt
2004-02-25 20:39 ` Sam Ravnborg
2004-02-25 19:45 ` Tom Rini
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=m3ishzqjd7.fsf@lugabout.jhcloos.org \
--to=cloos@jhcloos.com \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®