[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <49AE221D.9010909@s5r6.in-berlin.de>
Date: Wed, 04 Mar 2009 07:39:25 +0100
From: Stefan Richter <stefanr@...6.in-berlin.de>
To: Ingo Molnar <mingo@...e.hu>
CC: James Bottomley <James.Bottomley@...senPartnership.com>,
Jan Engelhardt <jengelh@...ozas.de>,
Boaz Harrosh <bharrosh@...asas.com>,
linux-scsi@...r.kernel.org,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
linux-rt-users@...r.kernel.org,
Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: Large amount of scsi-sgpool objects
Ingo Molnar wrote:
> * Stefan Richter <stefanr@...6.in-berlin.de> wrote:
>> Perhaps you could avoid putting such fixes into published
>> merge branches.
[so that consumers of the trees use them only on demand]
>
> Yeah, these commits are in none of the topic branches that are
> the git base of development, they are all already in a separate
> branch named "tip:out-of-tree".
So people should remember to retry without out-of-tree before reporting
problems == remember to report against the development base.
> That separate branch carries
> assorted fixlets for various bugs we trigger in -tip qa. It
> never goes upstream-wards, obviously. It's a bit like the
> fixlets portion of -mm.
Great, if an eye is kept on issues & resolutions tracking --- like in
this thread, only with less confusion. ;-)
--
Stefan Richter
-=====-==--= --== --=--
http://arcgraph.de/sr/
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists