[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1236150752.6049.19.camel@marge.simson.net>
Date: Wed, 04 Mar 2009 08:12:32 +0100
From: Mike Galbraith <efault@....de>
To: Stefan Richter <stefanr@...6.in-berlin.de>
Cc: Ingo Molnar <mingo@...e.hu>,
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
On Wed, 2009-03-04 at 07:39 +0100, Stefan Richter wrote:
> 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.
I'll bite, how does a gut-fu white belt accomplish that?
-Mike
--
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