DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:date:from:to:cc:subject:message-id:reply-to:references:mime-version:content-type:content-disposition:in-reply-to:user-agent;
        b=Iu/SyVIxyFdUm6bUCc2yuiWD7TobvaK7fXv5N3EbnqVn9RxXIHBM0QR5dYb0uiV0qNdE1o05qa8h5rQx9dk72cXYr7QMHYk/w/sYX1D6Tlx7OFDPK1ALBzb4/zlZF62YeyuokVPqtx2Ct5JJ03C03nI/pPfGj7ymhDdUF0kfgtg=
Date: Thu, 7 Jun 2007 23:40:08 +0800
From: WANG Cong <xiyou.wangcong@gmail.com>
To: Matt Mackall <mpm@selenic.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: <20070607154007.GA9305@localhost.localdomain>
Reply-To: WANG Cong <xiyou.wangcong@gmail.com>
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> <20070607140444.GR11115@waste.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20070607140444.GR11115@waste.org>
User-Agent: Mutt/1.4.2.1i
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1456
Lines: 42

On Thu, Jun 07, 2007 at 09:04:44AM -0500, Matt Mackall wrote:
>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.

Yes, I am using GPG's checking.

I think the most possible reason is that source file might be corrupted.
It's hardly the filesystem's fault, since I am using a stable kernel.

>
>Can you reproduce it?

May be very hard.;(

I deleted all the files of that version and download a new version to use.

Thanks!


-
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/