From: Jean Delvare <khali@linux-fr.org>
To: Xose Vazquez Perez <xose.vazquez@gmail.com>
Cc: linux-kernel@vger.kernel.org, pavel@suse.cz,
mchehab@infradead.org, linux@brodo.de, hch@lst.de,
arjan@linux.intel.com, kay.sievers@suse.de, rui.zhang@intel.com,
len.brown@intel.com, htejun@gmail.com, jengelh@computergmbh.de,
Michael Buesch <mb@bu3sch.de>,
gcosta@redhat.com, jirislaby@gmail.com, rene.herman@gmail.com,
ole@ans.pl, tglx@linutronix.de
Subject: Re: feature-removal-schedule.txt updated ??
Date: Sun, 29 Mar 2009 10:31:44 +0200 [thread overview]
Message-ID: <20090329103144.15091e79@hyperion.delvare> (raw)
In-Reply-To: <49CEC796.5040801@gmail.com>
Hi Xose,
On Sun, 29 Mar 2009 01:57:58 +0100, Xose Vazquez Perez wrote:
> Xose Vazquez Perez wrote:
>
> > code is still there or file is not updated ?
> >
> > $ grep ^When Documentation/feature-removal-schedule.txt | egrep -v "2009|2010|2.6.3[0-9]"
> > When: 2.6.29
> > When: July 2007
> > When: December 2008
> > When: November 2005
> > When: August 2006
> > When: before 2.6.19
> > When: October 2008
> > When: July 2008
> > When: August 2007
> > When: February 2008
> > When: Dec 2008
> > When: July 2008
> > When: 2.6.27
> > When: 2.6.29
> > When: After the only user (hal) has seen a release with the patches
> > When: 2.6.29
>
> today only ONE was fixed!!
This is all not very constructive. For one thing the merge window is
still open, so there are reasonable chances that more entries will be
removed in the next 9 days.
For another, flooding people that way isn't going to fix anything. If
you really want the situation to improve, you have to look at offending
entries individually, contact the responsible person individually, ask
why the entry is still there, and then send a patch removing or
updating it if needs be. This is constructive. Yelling "there are
out-of-date entries in Documentation/feature-removal-schedule.txt" is
not.
In other words, if you are sufficiently bothered by the current
situation and want it to change, then work on it yourself, on your own
time. We aren't your slaves, and we don't owe you anything.
Thanks,
--
Jean Delvare
prev parent reply other threads:[~2009-03-29 8:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-04 23:41 feature-removal-schedule.txt updated ?? Xose Vazquez Perez
2009-03-29 0:57 ` Xose Vazquez Perez
2009-03-29 2:03 ` Jan Engelhardt
2009-03-29 8:31 ` Jean Delvare [this message]
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=20090329103144.15091e79@hyperion.delvare \
--to=khali@linux-fr.org \
--cc=arjan@linux.intel.com \
--cc=gcosta@redhat.com \
--cc=hch@lst.de \
--cc=htejun@gmail.com \
--cc=jengelh@computergmbh.de \
--cc=jirislaby@gmail.com \
--cc=kay.sievers@suse.de \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@brodo.de \
--cc=mb@bu3sch.de \
--cc=mchehab@infradead.org \
--cc=ole@ans.pl \
--cc=pavel@suse.cz \
--cc=rene.herman@gmail.com \
--cc=rui.zhang@intel.com \
--cc=tglx@linutronix.de \
--cc=xose.vazquez@gmail.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