From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: Trying to get 2.6.5 kernel source
Date: Thu, 15 Apr 2004 05:33:59 +0000 [thread overview]
Message-ID: <16510.7879.884350.322808@napali.hpl.hp.com> (raw)
In-Reply-To: <0A78D025ACD7C24F84BD52449D8505A159CBB3@wcosmb01.cos.agilent.com>
>>>>> On Mon, 12 Apr 2004 18:03:01 -0700, Chris Wedgwood <cw@f00f.org> said:
Chris> On Tue, Apr 13, 2004 at 08:30:16AM +1000, Darren Williams
Chris> wrote:
>> ia64 2.6 is now part of the main stream kernel
Chris> [...]
Chris> perhaps some/all of the ia64 ports directories on the
Chris> kernel.org mirrors should either be renamed or at the very
Chris> least have README_PLEASE or similar inserted in so people
Chris> don't go erroneously looking about there
It's not an error to look in the ia64 directory, but yes, a README sounds
like a fine idea (assuming anybody reads them). I put something there.
Let's see if it'll help.
Thanks,
--david
prev parent reply other threads:[~2004-04-15 5:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-12 22:16 Trying to get 2.6.5 kernel source yiding_wang
2004-04-12 22:30 ` Darren Williams
2004-04-12 22:50 ` yiding_wang
2004-04-13 1:03 ` Chris Wedgwood
2004-04-15 5:33 ` David Mosberger [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=16510.7879.884350.322808@napali.hpl.hp.com \
--to=davidm@napali.hpl.hp.com \
--cc=linux-ia64@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