From: "H. Peter Anvin" <hpa@transmeta.com>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: Marcelo Tosatti <marcelo@conectiva.com.br>,
Phil Sorber <aafes@psu.edu>, lkml <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.4.16-pre1
Date: Sat, 24 Nov 2001 13:32:30 -0800 [thread overview]
Message-ID: <3C0011EE.3010401@transmeta.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0111241311040.2591-100000@penguin.transmeta.com>
Linus Torvalds wrote:
> On Sat, 24 Nov 2001, Marcelo Tosatti wrote:
>
>>>Are these going to appear on the front page of kernel.org?
>>>
>>They have to...
>>
>>I'm sure hpa will do that as soon as he has time to...
>>
>
> I also decided that the suggestion to move the "testing" subdirectory down
> to below the kernel that the directory is for is a good idea.
>
> So I moved all the 2.5.x testing stuff to kernel/v2.5/testing, leaving the
> old kernel/testing directory basically orphaned.
>
> Marcelo could either take over the old directory (which will make his
> pre-patches show up on kernel.org automatically), or preferably just do
> the same thing, and make the v2.4 test patches in v2.4/testing (which will
> also require support from the site admin, who is probably overworked as-is
> with the RAID failures ;)
>
> Linus
>
I like this idea much better than Marcelo's idea, which requires yet a
whole slew of ad hoc knowledge in the scripts -- there is just way too
much of that already. I'll try to implement this.
To summarize:
I'll expect v2.5 prepatches in v2.5/testing; v2.4 prepatches in
v2.4/testing, and nothing else...
-hpa
next prev parent reply other threads:[~2001-11-24 21:33 UTC|newest]
Thread overview: 103+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-24 18:39 Linux 2.4.16-pre1 Marcelo Tosatti
2001-11-24 18:40 ` Marcelo Tosatti
2001-11-24 20:36 ` Phil Sorber
2001-11-24 19:44 ` Marcelo Tosatti
2001-11-24 21:14 ` Linus Torvalds
2001-11-24 21:32 ` H. Peter Anvin [this message]
2001-11-24 22:04 ` François Cami
2001-11-26 0:49 ` Horst von Brand
2001-11-26 0:51 ` H. Peter Anvin
2001-11-26 17:50 ` Alan Cox
2001-11-26 18:08 ` H. Peter Anvin
2001-11-26 0:51 ` David Weinehall
2001-11-26 0:53 ` H. Peter Anvin
2001-11-25 1:56 ` Patrick McFarland
2001-11-25 2:12 ` Patrick McFarland
2001-11-25 2:34 ` war
2001-11-25 2:41 ` Patrick McFarland
2001-11-25 3:05 ` Mohammad A. Haque
2001-11-25 21:55 ` Patrick McFarland
2001-11-26 12:06 ` Martin Persson
2001-11-26 14:26 ` David Lang
2001-11-26 16:55 ` Alan Cox
2001-11-26 16:58 ` Dominik Kubla
2001-11-26 15:38 ` M. Edward (Ed) Borasky
2001-11-26 18:12 ` J Sloan
2001-11-25 4:10 ` J Sloan
2001-11-25 21:58 ` Patrick McFarland
2001-11-25 22:57 ` J Sloan
2001-11-25 23:11 ` Patrick McFarland
2001-11-26 0:26 ` Patrick McFarland
2001-11-26 0:31 ` Patrick McFarland
2001-11-26 0:39 ` CaT
2001-11-25 4:23 ` Victor Yodaiken
2001-11-25 3:04 ` John Alvord
2001-11-26 18:13 ` Alan Cox
2001-11-26 18:09 ` H. Peter Anvin
2001-11-24 20:58 ` Ryan Cumming
2001-11-24 22:21 ` H. Peter Anvin
2001-11-24 22:35 ` kernel.org maintenance Ahmed Masud
2001-11-24 22:56 ` Linux 2.4.16-pre1 Mohammad A. Haque
2001-11-24 21:09 ` Marc A. Ohmann
2001-11-24 19:54 ` Marcelo Tosatti
2001-11-24 21:13 ` Arnaldo Carvalho de Melo
2001-11-24 23:32 ` F.H. Bulthuis
2001-11-24 23:37 ` Rik van Riel
2001-11-24 23:47 ` F.H. Bulthuis
2001-11-25 13:34 ` Dominik Kubla
2001-11-25 14:15 ` Stephan von Krawczynski
2001-11-25 18:07 ` Tobias Ringstrom
2001-11-25 18:17 ` Linus Torvalds
2001-11-25 19:16 ` Stephan von Krawczynski
2001-11-25 22:07 ` Patrick McFarland
2001-11-25 19:27 ` Alex Bligh - linux-kernel
2001-11-25 22:13 ` Arnaldo Carvalho de Melo
2001-11-25 22:18 ` Patrick McFarland
2001-11-25 22:26 ` Arnaldo Carvalho de Melo
2001-11-25 22:31 ` Arnaldo Carvalho de Melo
2001-11-26 1:16 ` Mohammad A. Haque
2001-11-26 1:33 ` Patrick McFarland
2001-11-26 2:45 ` Mohammad A. Haque
2001-11-26 2:50 ` Horst von Brand
2001-11-27 0:47 ` Patrick McFarland
2001-11-27 1:01 ` Rik van Riel
2001-11-27 1:04 ` Patrick McFarland
2001-11-27 1:02 ` Andre Hedrick
2001-11-26 10:44 ` Rik van Riel
2001-11-26 6:57 ` Martin Eriksson
2001-11-25 22:28 ` François Cami
2001-11-25 22:36 ` Patrick McFarland
2001-11-25 22:40 ` Patrick McFarland
2001-11-26 0:20 ` Andrew Pimlott
2001-11-26 0:56 ` Patrick McFarland
2001-11-26 1:16 ` Phil Oester
2001-12-04 20:28 ` The Doctor What
2001-12-04 20:51 ` Rik van Riel
2001-11-25 23:53 ` [RFC] 2.5/2.6/2.7 transition [was Re: Linux 2.4.16-pre1] Mike Fedyk
2001-11-26 3:58 ` Linus Torvalds
2001-11-26 5:33 ` Mike Fedyk
2001-11-26 10:59 ` Rik van Riel
2001-11-26 14:58 ` jlnance
2001-11-26 18:18 ` H. Peter Anvin
2001-11-26 12:41 ` Horst von Brand
2001-11-26 19:35 ` Andrew Morton
2001-11-26 17:44 ` Rob Landley
2001-11-26 21:08 ` Alan Cox
2001-11-26 21:42 ` Rob Landley
2001-11-26 23:52 ` Rob Landley
2001-11-27 3:40 ` Johan Kullstam
2001-11-26 8:13 ` John Alvord
2001-11-25 14:39 ` Linux 2.4.16-pre1 Florian Weimer
2001-11-25 14:51 ` Russell King
2001-11-25 14:58 ` Florian Weimer
2001-11-25 15:06 ` Alexander Viro
2001-11-25 15:14 ` Bruce Harada
2001-11-25 21:44 ` Teodor Iacob
2001-11-25 21:24 ` Thiago Rondon
2001-11-25 21:51 ` Arnaldo Carvalho de Melo
2001-11-26 17:07 ` vda
2001-11-26 16:36 ` Charles Marslett
2001-11-27 4:30 ` Mike Fedyk
2001-11-27 8:59 ` Adrian Bunk
-- strict thread matches above, loose matches on Subject: below --
2001-11-24 21:56 Ricardo Galli
2001-11-25 12:09 Fred Bulthuis
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=3C0011EE.3010401@transmeta.com \
--to=hpa@transmeta.com \
--cc=aafes@psu.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
--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