linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@suse.de>
To: linux-scsi <linux-scsi@vger.kernel.org>,
	linux-ide <linux-ide@vger.kernel.org>,
	linux-fsdevel@vger.kernel.org, dm-devel@redhat.com
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Combined storage tree
Date: Fri, 10 Sep 2010 13:27:27 -0500	[thread overview]
Message-ID: <1284143247.6551.23.camel@mulgrave.site> (raw)

One of the requests from LSF10 in August was the production of a
combined storage tree.  This is now ready at

git://git.kernel.org/pub/scm/linux/kernel/git/jejb/storage-tree

It's actually a nightly built merge tree consisting of

scsi-misc; scsi-rc-fixes
libata#upstream-fixes, libata#upstream
block#for-linus, block#for-next
and the dm quilt (which is empty at the moment).

I haven't yet added vfs or any of the fs trees, but if necessary, I can.

Note, because it's built nightly, like linux-next, it's hard (but not
impossible) to use it as a basis for git trees (it is much easier to use
it as a basis for quilts).

If there are any cross-tree patch sets, I can add them in for this too.

The trees are labelled <linux-tree>-stor<n>

You can find the combined diffs to the base linus tree here:

http://www.kernel.org/pub/linux/kernel/people/jejb/storage-tree

(The build script and driving file are in the parent directory).

Any build cockups or missing trees, please let me know.

James



             reply	other threads:[~2010-09-10 18:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-10 18:27 James Bottomley [this message]
2010-09-11  8:20 ` Combined storage tree Dave Chinner
2010-09-11 13:55   ` James Bottomley
2010-09-13  2:58     ` Dave Chinner
2010-09-13 16:46       ` 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=1284143247.6551.23.camel@mulgrave.site \
    --to=james.bottomley@suse.de \
    --cc=dm-devel@redhat.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).