From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: linux-scsi <linux-scsi@vger.kernel.org>
Subject: SCSI git trees
Date: Wed, 29 Jul 2009 17:07:36 +0000 [thread overview]
Message-ID: <1248887256.3900.78.camel@mulgrave.site> (raw)
It seems I got unsubscribed from linux-scsi last week while I was on
holiday and I've likely missed a slew of patches, it seems like an
appropriate time to remind everyone how the SCSI trees work.
---
There are two git based scsi trees:
http://git.kernel.org/?p=linux/kernel/git/jejb/scsi-misc-2.6.git
called the scsi-misc tree for patches being collected for the next merge
window. And
http://git.kernel.org/?p=linux/kernel/git/jejb/scsi-rc-fixes-2.6.git
called scsi-fixes for bug fixes collected for current linux head.
Both trees are kept rebasable (no merge points) with all patches head at
the tree head (so you can use gitweb to see what's in them easily). Each
of the trees sends email to the author and all of the signoff chains
when a patch is added, so if you sent a patch in and haven't received an
email (and don't see it in either of the trees) I don't have it.
All trees feed into linux-next and all patches in scsi-misc/scsi-fixes
will be tested in linux-next for a few days before being passed on to
Linus (so no more patches get added at that point).
James
next reply other threads:[~2009-07-29 17:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-29 17:07 James Bottomley [this message]
2009-08-03 17:52 ` SCSI git trees John Stoffel
2009-08-03 18:09 ` Randy Dunlap
2009-08-03 19:00 ` James Bottomley
2009-08-03 18:57 ` James Bottomley
2009-08-03 19:13 ` John Stoffel
2009-08-03 20:27 ` Jens Axboe
2009-08-03 21:00 ` John Stoffel
2009-08-03 21:04 ` Jens Axboe
2009-08-04 16:37 ` John Stoffel
2009-08-04 20:15 ` Jens Axboe
2009-08-04 20:27 ` John Stoffel
2009-08-04 20:36 ` Jens Axboe
2009-08-04 20:45 ` John Stoffel
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=1248887256.3900.78.camel@mulgrave.site \
--to=james.bottomley@hansenpartnership.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