Date: Thu, 7 Jun 2007 09:04:44 -0500
From: Matt Mackall <mpm@selenic.com>
To: WANG Cong <xiyou.wangcong@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>, linux-kernel@vger.kernel.org,
       Rusty Russell <rusty@rustcorp.com.au>
Subject: Re: 2.6.22-rc4-mm1
Message-ID: <20070607140444.GR11115@waste.org>
References: <20070606020737.4663d686.akpm@linux-foundation.org> <20070606161936.GA8952@localhost.localdomain> <20070606110931.fda845de.akpm@linux-foundation.org> <20070607022608.GA2416@localhost.localdomain> <20070607055912.GX11166@waste.org> <20070607065158.GA1996@localhost.localdomain>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20070607065158.GA1996@localhost.localdomain>
User-Agent: Mutt/1.5.13 (2006-08-11)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1141
Lines: 30

On Thu, Jun 07, 2007 at 02:51:58PM +0800, WANG Cong wrote:
> >> Maybe there's something wrong with ketchup. ;(
> >
> >Can you do an 'lsdiff | grep lguest' on the patch in your ~/.ketchup directory?
> >
> >Ketchup simply applies patches, it never touches filenames directly.
> >So for something to go wrong here and drop a file in the tree with a
> >damaged pathname, you've either got a damaged patch, a bug in patch
> >itself, or some form of filesystem corruption.
> 
> Thanks for your point.
> 
> It should be Documentation/lguest/lguest.c, maybe it was corrupted and ketchup
> backuped it as mlguest.c.

It'd be interesting to figure out how that happened, still.

If your patch file is intact (are you using GPG's signature-checking
support?), the most likely explanation is an operating system or
filesystem bug.

Can you reproduce it?

-- 
Mathematics is the supreme nostalgia of our time.
-
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/