Message-ID: <BAYC1-PASMTP01E922231EF198D3EF563EAE3E0@CEZ.ICE>
Date: Wed, 30 Aug 2006 10:00:15 -0400
From: Sean <seanlkml@sympatico.ca>
To: Willy Tarreau <w@1wt.eu>
Cc: Andi Kleen <ak@suse.de>, davej@redhat.com, pageexec@freemail.hu,
       linux-kernel@vger.kernel.org
Subject: Re: [PATCH][RFC] exception processing in early boot
Message-Id: <20060830100015.6b967c32.seanlkml@sympatico.ca>
In-Reply-To: <20060830131612.GB351@1wt.eu>
References: <20060830063932.GB289@1wt.eu>
	<p73y7t65z6c.fsf@verdi.suse.de>
	<20060830121845.GA351@1wt.eu>
	<200608301459.15008.ak@suse.de>
	<20060830131612.GB351@1wt.eu>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 885
Lines: 21

On Wed, 30 Aug 2006 15:16:12 +0200
Willy Tarreau <w@1wt.eu> wrote:

> That's already what I'm doing, and yes, it is *that* hard. We're literally
> speaking about *thousands* of patches. It's as difficult to find one patch
> within 2.6 git changes as it is to find a useful mail in the middle of 99%
> spam. This is not because of GIT but because of the number of changes.

Willy,

The git-cherry command might be useful for you in this situation.  It will
show you all the patches in one branch that have been merged in an upstream
branch, and those that haven't.  Not sure if it's perfect for your situation,
but may be worth a look.

Sean
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/