From: Jeff Garzik <jeff@garzik.org>
To: "linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>, Linus Torvalds <torvalds@osdl.org>
Subject: libata-dev.git frozen
Date: Sat, 30 Sep 2006 23:51:15 -0400 [thread overview]
Message-ID: <451F3B33.3080000@garzik.org> (raw)
Similar to the netdev announcement, libata-dev.git is now closed to new
features.
Though really, [my fault] I should have posted this as soon as the merge
window opened. The stuff that goes into each new release, when the
merge window opens, should be stuff that has already been through a
round of testing in -mm.
The updates presented in #upstream -- just minor stuff, really -- will
go upstream tomorrow. Everything else will be fixes.
And the message for the future is: don't wait until the merge window
opens, to submit your code. Doing so means it doesn't get the normal
amount of testing and review, and is thus discouraged.
Jeff
next reply other threads:[~2006-10-01 3:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-01 3:51 Jeff Garzik [this message]
[not found] ` <45202B9E.50503@gmx.net>
2006-10-02 15:20 ` libata-dev.git frozen Uwe Koziolek
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=451F3B33.3080000@garzik.org \
--to=jeff@garzik.org \
--cc=akpm@osdl.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.org \
/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;
as well as URLs for NNTP newsgroup(s).