public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bill Davidsen <davidsen@tmr.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Linux v2.6.8 - Oops on NFSv3
Date: Mon, 16 Aug 2004 18:39:45 -0400	[thread overview]
Message-ID: <cfrcnp$9bd$2@gatekeeper.tmr.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0408140404050.1839@ppc970.osdl.org>

Linus Torvalds wrote:
> 
> On Sat, 14 Aug 2004, Christoph Hellwig wrote:
> 
>>Cane we make this 2.6.9 to avoid breaking all kinds of scripts expecting
>>three-digit kernel versions?
> 
> 
> Well, we've been discussing the 2.6.x.y format for a while, so I see this 
> as an opportunity to actually do it... Will it break automated scripts? 
> Maybe. But on the other hand, we'll never even find out unless we try it 
> some time.

So will we see 2.6.8.1-bk1 tomorrow, or 2.6.8-bk1.1, or ??? And what 
will 2.6.8.3 patch against, 2.6.8.2 or 2.6.8?

I think you are perhaps over-solving the problem that an early -bk1 
could have solved without breaking scripts and kernel macros.

-- 
    -bill davidsen (davidsen@tmr.com)
"The secret to procrastination is to put things off until the
  last possible moment - but no longer"  -me

  parent reply	other threads:[~2004-08-16 22:39 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-14  6:05 Linux v2.6.8 Linus Torvalds
2004-08-14 10:10 ` Linux v2.6.8 - Oops on NFSv3 Willy Tarreau
2004-08-14 10:19   ` Willy Tarreau
2004-08-14 10:34   ` Jeff Garzik
2004-08-14 10:41   ` Linus Torvalds
2004-08-14 10:35     ` Willy Tarreau
2004-08-14 10:49     ` Linus Torvalds
2004-08-14 10:55       ` Christoph Hellwig
2004-08-14 11:05         ` Linus Torvalds
2004-08-14 11:18           ` Arjan van de Ven
2004-08-14 11:27             ` Jeff Garzik
2004-08-14 11:31             ` viro
2004-08-14 12:48           ` Nur Hussein
2004-08-14 20:57             ` Greg Norris
2004-08-18 20:57               ` [PATCH] scripts/patch-kernel: use EXTRAVERSION Randy.Dunlap
2004-08-22 20:40                 ` Sam Ravnborg
2005-03-15 16:15                   ` [BUG] " David Greaves
2005-03-15 16:25                     ` Greg KH
2005-03-15 17:44                       ` Greg KH
2005-03-15 17:54                         ` Matt Mackall
2005-03-15 19:55                           ` Sam Ravnborg
2005-03-15 18:02                       ` David Greaves
2005-03-15 18:37                         ` Sam Ravnborg
2005-04-12  0:07                     ` [PATCH] scripts/patch-kernel: EXTRAVERSION patches are not incremental Randy.Dunlap
2004-08-17  3:13             ` Linux v2.6.8 - Oops on NFSv3 Patrick McFarland
2004-08-14 17:20           ` Matt Mackall
2004-08-15 20:10             ` Marcelo Tosatti
2004-08-16  3:37           ` Han Boetes
2004-08-16 14:06           ` Daniel Jacobowitz
2004-08-16 22:39           ` Bill Davidsen [this message]
2004-08-18  8:29           ` Robert Schwebel
2004-08-14 15:33       ` Norman Zhang
2004-08-14 10:19 ` [patch 2.6.8-rc4-mm1] via-velocity: wrong module name in Kconfig documentation Francois Romieu
2004-09-20 18:44   ` Jeff Garzik
2004-08-14 10:30 ` Linux v2.6.8 Jeff Garzik
2004-08-14 11:19   ` Stephan von Krawczynski
2004-08-14 11:38     ` Francois Romieu
2004-08-14 11:16 ` William Lee Irwin III
2004-08-16 17:56 ` Linux v2.6.8 (compile stats) John Cherry

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='cfrcnp$9bd$2@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