From: Sam Ravnborg <sam@ravnborg.org>
To: Thomas Molina <tmolina@copper.net>
Cc: Andries Brouwer <aebr@win.tue.nl>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] README change
Date: Thu, 28 Nov 2002 21:02:08 +0100 [thread overview]
Message-ID: <20021128200208.GB11043@mars.ravnborg.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0211280901350.1023-100000@lap.molina>
On Thu, Nov 28, 2002 at 09:03:14AM -0600, Thomas Molina wrote:
While you are add it, how about introducing "make help" in the README.
At least for a few architectures it list possible targets.
And bzImage is not the only one.
Sam
prev parent reply other threads:[~2002-11-28 19:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-28 0:26 [PATCH] README change Thomas Molina
2002-11-28 2:08 ` Barry K. Nathan
2002-11-28 3:26 ` Thomas Molina
2002-12-02 19:20 ` Denis Vlasenko
2002-11-28 13:34 ` Andries Brouwer
2002-11-28 15:03 ` Thomas Molina
2002-11-28 20:02 ` Sam Ravnborg [this message]
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=20021128200208.GB11043@mars.ravnborg.org \
--to=sam@ravnborg.org \
--cc=aebr@win.tue.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=tmolina@copper.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.