[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20081110102607.378c3279.sfr@canb.auug.org.au>
Date: Mon, 10 Nov 2008 10:26:07 +1100
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Boaz Harrosh <bharrosh@...asas.com>
Cc: Andrew Morton <akpm@...ux-foundation.org>,
James.Bottomley@...senPartnership.com, linux-next@...r.kernel.org,
Sam Ravnborg <sam@...nborg.org>, michaelc@...wisc.edu,
fujita.tomonori@....ntt.co.jp, jeff@...zik.org,
osd-dev@...n-osd.org, linux-scsi@...r.kernel.org,
Sami.Iren@...gate.com, Pete Wyckoff <pw@...d.com>,
linux-kernel@...r.kernel.org
Subject: Re: [PATCHSET 00/18] open-osd: OSD Initiator library for Linux
Hi Boaz,
On Sun, 09 Nov 2008 16:58:59 +0200 Boaz Harrosh <bharrosh@...asas.com> wrote:
>
> I have prepared a branch for linux-next based on today's Linus tree
> It is here:
> git://git.open-osd.org/linux-open-osd.git linux-next
> This is if it's OK with James, as these bits are his responsibility.
> They need only sit in linux-next for a couple of weeks to get some wider
> compilation exposure. Other then that they are totally new code and
> are safe. Eventually they should be included into Linux-next through
> scsi-misc-2.6.
I have added that tree to linux-next for today.
What I say to everyone: commits in that branch must have been posted
somewhere appropriate, reviewed, unit tested and destined for the next
merge window. Also, note that my (new) practise is to temporarily drop a
tree if it causes non-trivial conflicts (especially with Linus' tree), so
don't be too upset if you get a message from me to that effect.
--
Cheers,
Stephen Rothwell sfr@...b.auug.org.au
http://www.canb.auug.org.au/~sfr/
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists