From: Jeff Garzik <jgarzik@pobox.com>
To: dcinege@psychosis.com
Cc: landley@trommello.org, linux-kernel@vger.kernel.org,
reiser@namesys.com, alan@lxorguk.ukuu.org.uk, davem@redhat.com,
boissiere@adiglobal.com
Subject: Re: Abbott and Costello meet Crunch Time -- Penultimate 2.5 merge candidate list.
Date: Wed, 30 Oct 2002 02:40:05 -0500 [thread overview]
Message-ID: <3DBF8CD5.1030306@pobox.com> (raw)
In-Reply-To: 200210300229.44865.dcinege@psychosis.com
Dave Cinege wrote:
>On Sunday 27 October 2002 21:17, Rob Landley wrote:
>
>
>>This is the next to last posting of this list. (When abbott and costello
>>meet the monster, its time is almost up.) There will be at most one more,
>>tomorrow, and it may just be a repost of this cc'd to Linus. (Those
>>of you waiting for the last minute, this would be it.)
>>
>>
>
>Knock off initramfs off...I'll be posting something that
>supercedes it (IMO) within the next 72 hours.
>
>Aside from providing full untar suppprt, it DRAMATICALLY
>cleans up do_mounts.c and moves all the initrd code that was
>there to initrd.c. Infact I pretty much entirly rewrote initrd,
>so it makes sense. (purging prehistoric junk, etc.)
>
>
lol
untar - cpio is better.
initrd - 99% moved out of the kernel
do_mounts - moved out of the kernel completely
initramfs - should be ready for Linus in the next day or so.
None of that junk -- and a whole lot more -- needs to be in the kernel
at all.
Jeff
next prev parent reply other threads:[~2002-10-30 7:34 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-28 2:17 Abbott and Costello meet Crunch Time -- Penultimate 2.5 merge candidate list Rob Landley
2002-10-28 8:25 ` Vamsi Krishna S .
2002-10-28 9:55 ` Skip Ford
2002-10-28 10:35 ` Vamsi Krishna S .
2002-10-28 10:29 ` Andrew Walrond
2002-10-28 10:40 ` Rob Landley
2002-10-28 12:15 ` Nicholas Wourms
2002-10-28 13:31 ` Dave Jones
2002-10-28 14:05 ` Andrew Walrond
2002-10-28 14:42 ` Andrew Walrond
2002-10-28 15:02 ` Alan Cox
2002-10-30 7:29 ` Dave Cinege
2002-10-30 7:40 ` Jeff Garzik [this message]
2002-10-30 8:22 ` Dave Cinege
2002-10-30 8:37 ` Russell King
2002-10-30 9:32 ` Dave Cinege
2002-10-30 8:41 ` Jeff Garzik
2002-10-30 8:51 ` Erik Andersen
2002-10-30 9:00 ` Miles Bader
2002-10-30 9:06 ` Jeff Garzik
2002-10-30 9:19 ` Miles Bader
2002-10-30 9:26 ` Jeff Garzik
2002-10-30 9:38 ` Miles Bader
2002-10-30 9:42 ` Erik Andersen
2002-10-30 10:50 ` Jeff Garzik
2002-10-30 9:34 ` Russell King
2002-10-30 10:07 ` Dave Cinege
2002-10-30 9:36 ` Erik Andersen
2002-10-30 10:52 ` Jeff Garzik
2002-10-30 9:55 ` Dave Cinege
2002-10-30 9:59 ` Miles Bader
2002-10-30 10:24 ` Dave Cinege
2002-10-30 10:05 ` Jeff Garzik
2002-10-30 10:14 ` Dave Cinege
2002-10-30 10:24 ` Jeff Garzik
2002-10-30 10:42 ` Dave Cinege
2002-10-30 11:06 ` Jeff Garzik
2002-10-30 9:55 ` Dave Cinege
2002-10-30 10:29 ` Jeff Garzik
2002-11-04 2:13 ` Rob Landley
2002-11-04 7:39 ` Help needed with IRQ on Ali chipset Jacek Pliszka
2002-11-04 13:10 ` Abbott and Costello meet Crunch Time -- Penultimate 2.5 merge candidate list Alan Cox
2002-11-04 22:52 ` Werner Almesberger
2002-11-04 23:02 ` Jeff Garzik
2002-11-04 18:16 ` Rob Landley
2002-11-04 23:22 ` Werner Almesberger
2002-10-30 14:32 ` Alan Cox
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=3DBF8CD5.1030306@pobox.com \
--to=jgarzik@pobox.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=boissiere@adiglobal.com \
--cc=davem@redhat.com \
--cc=dcinege@psychosis.com \
--cc=landley@trommello.org \
--cc=linux-kernel@vger.kernel.org \
--cc=reiser@namesys.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