From: Ian Molton <spyro@armlinux.org>
To: "Petr Vandrovec" <VANDROVE@vc.cvut.cz>
Cc: phillips@bonn-fries.net, lm@bitmover.com, linux-kernel@vger.kernel.org
Subject: Re: BK, deltas, snapshots and fate of -pre...
Date: Mon, 22 Apr 2002 19:19:53 +0100 [thread overview]
Message-ID: <20020422191953.034f51d4.spyro@armlinux.org> (raw)
In-Reply-To: <31CB8B22019@vcnet.vc.cvut.cz>
Petr Vandrovec Awoke this dragon, who will now respond:
>
> Why we have kernel tarball at all, then? Just put URLs where you can
> download different pieces of kernel, and we are done. You finally
Actually, the kernel tarball is full of crap we dont need.
Sooner or later its going to get too big and be split up into
core kernel
drivers (drivers/net, drivers/video etc.)
arch specifics
documentation
all for seperate download.
next prev parent reply other threads:[~2002-04-22 18:12 UTC|newest]
Thread overview: 125+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-22 17:45 BK, deltas, snapshots and fate of -pre Petr Vandrovec
2002-04-22 18:19 ` Ian Molton [this message]
2002-04-22 18:20 ` Anton Altaparmakov
2002-04-22 18:31 ` Thunder from the hill
2002-04-22 19:40 ` Roman Zippel
2002-04-22 19:44 ` Larry McVoy
[not found] <mailman.1019594711.6915.linux-kernel2news@redhat.com>
2002-04-24 0:37 ` Pete Zaitcev
-- strict thread matches above, loose matches on Subject: below --
2002-04-23 0:35 Chris Adams
2002-04-21 14:25 Andries.Brouwer
2002-04-21 3:46 [PATCH] Remove Bitkeeper documentation from Linux tree Ian Molton
2002-04-21 4:05 ` BK, deltas, snapshots and fate of -pre Alexander Viro
2002-04-21 1:53 ` Rob Landley
2002-04-21 18:40 ` Linus Torvalds
2002-04-21 23:08 ` Pavel Machek
2002-04-24 2:23 ` Linus Torvalds
2002-04-21 3:59 ` David S. Miller
2002-04-21 4:32 ` Andrew Morton
2002-04-21 5:59 ` Andreas Dilger
2002-04-21 4:13 ` Linus Torvalds
2002-04-21 12:53 ` Daniel Phillips
2002-04-22 15:44 ` Larry McVoy
2002-04-21 15:50 ` Daniel Phillips
2002-04-22 16:10 ` Larry McVoy
2002-04-21 16:21 ` Daniel Phillips
2002-04-22 17:17 ` Larry McVoy
2002-04-21 17:34 ` Daniel Phillips
2002-04-22 17:38 ` Larry McVoy
2002-04-21 17:49 ` Daniel Phillips
2002-04-22 17:53 ` Larry McVoy
2002-04-21 18:09 ` Daniel Phillips
2002-04-22 19:53 ` Doug Ledford
2002-04-21 20:29 ` Daniel Phillips
2002-04-22 20:53 ` Doug Ledford
2002-04-21 21:05 ` Daniel Phillips
2002-04-22 21:21 ` Doug Ledford
2002-04-21 21:37 ` Daniel Phillips
2002-04-22 21:45 ` Alexander Viro
2002-04-22 22:49 ` Larry McVoy
2002-04-22 22:08 ` Doug Ledford
2002-04-22 22:25 ` Jeff Garzik
2002-04-22 21:25 ` Jeff Garzik
2002-04-22 21:30 ` Doug Ledford
2002-04-22 21:33 ` Nicholas Harring
2002-04-25 20:53 ` Kai Henningsen
2002-04-21 23:16 ` Pavel Machek
2002-04-23 20:45 ` Rik van Riel
2002-04-25 3:51 ` Ian Molton
2002-04-25 3:55 ` Olivier Galibert
2002-04-25 12:38 ` Ian Molton
2002-04-25 13:33 ` David Woodhouse
2002-04-25 14:29 ` Richard Gooch
2002-04-25 15:41 ` Rik van Riel
2002-04-22 17:31 ` Jeff Garzik
2002-04-27 18:59 ` Richard Gooch
2002-04-26 20:19 ` Daniel Phillips
2002-04-28 17:42 ` Richard Gooch
2002-04-26 20:38 ` Daniel Phillips
2002-04-28 17:52 ` Richard Gooch
2002-04-27 20:02 ` Roman Zippel
2002-04-28 17:40 ` Richard Gooch
2002-04-28 18:08 ` Linus Torvalds
2002-04-28 18:47 ` Richard Gooch
2002-04-28 19:07 ` Kiss The Blade
2002-04-28 19:27 ` Linus Torvalds
2002-04-28 19:41 ` Richard Gooch
2002-04-28 19:49 ` Kiss The Blade
2002-04-28 19:42 ` Richard Gooch
2002-04-28 20:03 ` tomas szepe
2002-04-28 20:11 ` Roman Zippel
2002-04-28 20:40 ` Kiss The Blade
2002-04-29 6:55 ` Kai Henningsen
2002-04-29 6:55 ` Kai Henningsen
2002-04-28 20:06 ` Roman Zippel
2002-04-27 20:40 ` Larry McVoy
2002-04-22 17:10 ` Jeff Garzik
2002-04-21 17:17 ` Daniel Phillips
2002-04-22 17:19 ` Jeff Garzik
2002-04-21 17:37 ` Daniel Phillips
2002-04-22 17:46 ` Jeff Garzik
2002-04-22 17:21 ` Larry McVoy
2002-04-21 17:44 ` Daniel Phillips
2002-04-22 17:48 ` Larry McVoy
2002-04-21 18:03 ` Daniel Phillips
2002-04-22 17:52 ` Jeff Garzik
2002-04-21 18:05 ` Daniel Phillips
2002-04-22 20:18 ` Jeff Garzik
2002-04-21 20:42 ` Daniel Phillips
2002-04-22 20:57 ` Jeff Garzik
2002-04-21 21:06 ` Daniel Phillips
2002-04-22 20:57 ` Anton Altaparmakov
2002-04-22 18:01 ` Anton Altaparmakov
2002-04-21 18:16 ` Daniel Phillips
2002-04-22 18:29 ` Anton Altaparmakov
2002-04-21 18:47 ` Daniel Phillips
2002-04-22 19:41 ` Anton Altaparmakov
2002-04-23 4:57 ` Andre Pang
2002-04-22 11:34 ` Daniel Phillips
2002-04-23 5:56 ` Andreas Dilger
2002-04-21 4:31 ` Ian Molton
2002-04-21 4:20 ` David S. Miller
2002-04-21 4:42 ` Ian Molton
2002-04-21 4:29 ` David S. Miller
2002-04-21 4:49 ` Ben Greear
2002-04-21 6:27 ` Alexander Viro
2002-04-21 11:18 ` Ian Molton
2002-04-21 16:28 ` dean gaudet
2002-04-21 12:57 ` Daniel Phillips
2002-04-21 4:40 ` Skip Ford
2002-04-21 8:31 ` Russell King
2002-04-21 13:05 ` Daniel Phillips
2002-04-22 13:08 ` Russell King
2002-04-21 20:53 ` Skip Ford
2002-04-21 16:35 ` dean gaudet
2002-04-21 17:13 ` Jeff Garzik
2002-04-21 17:23 ` Larry McVoy
2002-04-21 17:32 ` Jeff Garzik
2002-04-21 17:39 ` Larry McVoy
2002-04-21 17:45 ` Jeff Garzik
2002-04-21 17:47 ` Larry McVoy
2002-04-21 17:49 ` Jeff Garzik
2002-04-21 17:57 ` Larry McVoy
2002-04-21 18:07 ` Jeff Garzik
2002-04-21 18:14 ` Larry McVoy
2002-04-21 18:24 ` Jeff Garzik
2002-04-21 18:26 ` Larry McVoy
2002-04-22 6:33 ` Rusty Russell
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=20020422191953.034f51d4.spyro@armlinux.org \
--to=spyro@armlinux.org \
--cc=VANDROVE@vc.cvut.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=lm@bitmover.com \
--cc=phillips@bonn-fries.net \
/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