[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4818ED61.9020002@gmail.com>
Date: Thu, 01 May 2008 00:06:25 +0200
From: Jiri Slaby <jirislaby@...il.com>
To: Dmitri Vorobiev <dmitri.vorobiev@...il.com>
CC: Andrew Morton <akpm@...ux-foundation.org>,
Linus Torvalds <torvalds@...ux-foundation.org>, rjw@...k.pl,
davem@...emloft.net, linux-kernel@...r.kernel.org,
Ingo Molnar <mingo@...e.hu>
Subject: Re: Slow DOWN, please!!!
On 04/30/2008 11:42 PM, Dmitri Vorobiev wrote:
> For busy (or lazy) people like myself, the big problem with linux-next are
> the frequent merge breakages, when pulling the tree stops with "you are in
> the middle of a merge conflict". Perhaps, there is a better way to resolve
> this without just removing the whole repo and cloning it once again - this
If this is still an issue of -next, I would say we won't get too much testers. I
gave up after first time I was attacked by that and got back to pure -mm.
I think greg-kh asked why this happens (Stephen rebases?), if you search
archives, I'm sure you'll find it.
--
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