public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: davidsen@tmr.com (bill davidsen)
To: linux-kernel@vger.kernel.org
Subject: Re: Linux v2.4.19
Date: 7 Aug 2002 01:54:33 GMT	[thread overview]
Message-ID: <aipukp$9bg$1@gatekeeper.tmr.com> (raw)
In-Reply-To: 1028413405.1761.38.camel@irongate.swansea.linux.org.uk

In article <1028413405.1761.38.camel@irongate.swansea.linux.org.uk>,
Alan Cox  <alan@lxorguk.ukuu.org.uk> wrote:
| On Sat, 2002-08-03 at 22:00, Ged Haywood wrote:
| > Hi there,
| > 
| > On Sat, 3 Aug 2002, Mr. James W. Laferriere wrote:
| > 
| > > Haven't the tarballs usuaully been archived as 'linux/' instead of
| > > 'linux-2.4.19/' ?
| > 
| > Absolutely not.  Many systems have a symlink 'linux' to the current
| > kernel tree, which is a directory e.g. 'linux-2.2.16'.  If the tarball
| 
| Kernels until recently did always unpack into linux/. Linus changed and
| I'm happy Marcelo has followed suit, its much more sensible the new way

Let's hope the major fix trees like -aa and -ac follow the convention. I
have no problem with the change (since I keep my stuff that way) but I
hope it is pervasive.
-- 
bill davidsen <davidsen@tmr.com>
  CTO, TMR Associates, Inc
Doing interesting things with little computers since 1979.

      reply	other threads:[~2002-08-07  1:56 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-03  0:15 Linux v2.4.19 Marcelo Tosatti
2002-08-03 11:45 ` Harald Dunkel
2002-08-03 12:18   ` Harald Dunkel
2002-08-03 12:32     ` Thunder from the hill
2002-08-03 12:40       ` Harald Dunkel
2002-08-05 18:00         ` Tom Rini
2002-08-03 19:27 ` Mr. James W. Laferriere
2002-08-03 21:00   ` Ged Haywood
2002-08-03 22:23     ` Alan Cox
2002-08-07  1:54       ` bill davidsen [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='aipukp$9bg$1@gatekeeper.tmr.com' \
    --to=davidsen@tmr.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