From: James Bottomley <James.Bottomley@steeleye.com>
To: SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: 2.6.0 stability and the BK scsi trees
Date: 16 Oct 2003 06:29:28 +0530 [thread overview]
Message-ID: <1066265974.16761.426.camel@fuzzy> (raw)
In the light of the recently announced "bug fixes only" edict for the
2.6 kernel, I'll be splitting our current SCSI BK tree:
bk://linux-scsi.bkbits.net/scsi-misc-2.5
Into two trees. One:
bk://linux-scsi.bkbits.net/scsi-bugfixes-2.6
for upstream inclusion, and the other
bk://linux-scsi.bkbits.net/scsi-misc-2.7
To hold all the other stuff for eventual inclusion in 2.7.
I'll be on Holiday until 22 October, but I'll try to do this shortly
after I get back home.
If you send any patches to the SCSI list in the mean time, could you
make sure you label them "bug fix" (and make sure they really are) if
they are for immediate inclusion.
Thanks,
James
next reply other threads:[~2003-10-16 0:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-16 0:59 James Bottomley [this message]
2003-10-16 11:56 ` 2.6.0 stability and the BK scsi trees Douglas Gilbert
2003-10-16 13:28 ` Matthew Wilcox
2003-10-18 15:24 ` Patrick Mansfield
2003-10-18 16:38 ` Matthew Wilcox
2003-10-20 14:54 ` Badari Pulavarty
2003-10-17 12:31 ` Christoph Hellwig
2003-10-22 14:23 ` James Bottomley
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=1066265974.16761.426.camel@fuzzy \
--to=james.bottomley@steeleye.com \
--cc=linux-scsi@vger.kernel.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