From: Rob Landley <rob@landley.net>
To: "Robert P. J. Day" <rpjday@mindspring.com>
Cc: Randy Dunlap <randy.dunlap@oracle.com>,
lkml <linux-kernel@vger.kernel.org>,
akpm <akpm@linux-foundation.org>,
bos@serpentine.com, werner@almesberger.net, hpa@zytor.com
Subject: Re: [PATCH] docs: ramdisk/initrd/initramfs corrections
Date: Thu, 30 Aug 2007 18:36:48 -0500 [thread overview]
Message-ID: <200708301836.48707.rob@landley.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0708301426360.4088@localhost.localdomain>
On Thursday 30 August 2007 1:28:17 pm Robert P. J. Day wrote:
> On Thu, 30 Aug 2007, Randy Dunlap wrote:
>
> ...
>
> > The old "ramdisk=<ram_size>" has been changed to
> > "ramdisk_size=<ram_size>" to make it clearer. The original
> > "ramdisk=<ram_size>" has been kept around for compatibility reasons,
> > but it may be removed in the future.
>
> ...
>
> i just the other day submitted a patch to remove that backward
> compatibility, and the m68k portion of it has already been acked by
> geert uytterhoeven.
Could you mention it in feature-removal-schedule.txt? (People check that for
warning of upcoming changes that impact existing code. They may not notice
something elsewhere after they've got it working...)
(Also, sorting feature-removal-schedule.txt by date would be really nice. The
sucker's gotten huge...)
And while I'm looking at this, is there some other place that entries in this
file go once they _have_ been removed, so people can see "oh yeah, that went
away in 2.6.23) when they try to install 2.6.25? If there is, I missed it.
Maybe http://lwn.net/Articles/2.6-kernel-api/ is good enough, but this seems
easy to do in Documentation...
Thanks,
Rob
--
"One of my most productive days was throwing away 1000 lines of code."
- Ken Thompson.
next prev parent reply other threads:[~2007-08-30 22:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-30 18:20 [PATCH] docs: ramdisk/initrd/initramfs corrections Randy Dunlap
2007-08-30 18:28 ` Robert P. J. Day
2007-08-30 23:36 ` Rob Landley [this message]
2007-08-30 22:41 ` H. Peter Anvin
2007-08-30 23:13 ` Randy Dunlap
2007-08-30 23:21 ` H. Peter Anvin
2007-08-31 5:41 ` Robert P. J. Day
2007-08-31 5:34 ` Robert P. J. Day
2007-09-02 8:26 ` Geert Uytterhoeven
2007-08-31 7:29 ` Robert P. J. Day
2007-08-31 14:25 ` Valdis.Kletnieks
2007-08-31 14:20 ` Robert P. J. Day
2007-08-30 19:13 ` Bryan O'Sullivan
2007-08-30 23:29 ` Rob Landley
2007-08-31 0:00 ` Jesper Juhl
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=200708301836.48707.rob@landley.net \
--to=rob@landley.net \
--cc=akpm@linux-foundation.org \
--cc=bos@serpentine.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
--cc=rpjday@mindspring.com \
--cc=werner@almesberger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.