public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Morten Helgesen <morten.helgesen@nextframe.net>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Incorrect 2.5.45 tar-balls created..
Date: Wed, 30 Oct 2002 05:35:20 +0100	[thread overview]
Message-ID: <20021030053520.A109@sexything> (raw)
In-Reply-To: <Pine.LNX.4.44.0210291957330.1626-100000@home.transmeta.com>

Hey Chief, 

On Tue, Oct 29, 2002 at 08:03:33PM -0800, Linus Torvalds wrote:
> 
> There was, for a while, bogus 2.5.45 tar-balls etc created from a BK tree
> that was never meant to be exported (translation: "Linus ran his automatic
> release-scripts on a bad tree because he is a booger-head").
> 
> I've removed the offending files, and hopefully nobody even had time to
> download them, but just in case - if you get your kernels as tar-balls (or 
> as old-fashioned patches) rather than from the BK tree, and you saw a 
> 2.5.45, you should ignore it.

hehe - I got it from kernel.org and even sent off a one-liner against 
it to fix an error in net/ipv4/syncookies.c before I saw your mail ...

As I saw Roman`s mail about kernel conf 1.3 ("Update to 2.5.45") I thought
"Cool!" and got 2.5.45.tar.gz right away ... hehe - anyway, no harm done ... 
The image didn`t boot though, so I guess I`ll wait until
you release a _real_ 2.5.45 before doing more testing. 

> 
> 		Linus "booger-head" Torvalds
> 

== Morten

-- 

"Livet er ikke for nybegynnere" - sitat fra en klok person.

mvh
Morten Helgesen 
UNIX System Administrator & C Developer 
Nextframe AS
admin@nextframe.net / 93445641
http://www.nextframe.net

      reply	other threads:[~2002-10-30  4:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-30  4:03 Incorrect 2.5.45 tar-balls created Linus Torvalds
2002-10-30  4:35 ` Morten Helgesen [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=20021030053520.A109@sexything \
    --to=morten.helgesen@nextframe.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.com \
    /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