[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20071116201017.GA11330@suse.de>
Date: Fri, 16 Nov 2007 12:10:17 -0800
From: Greg KH <gregkh@...e.de>
To: Matti Aarnio <matti.aarnio@...iler.org>
Cc: Mark Lord <lkml@....ca>, linux-kernel@...r.kernel.org,
Andrew Morton <akpm@...ux-foundation.org>,
torvalds@...ux-foundation.org, stable@...nel.org
Subject: Re: Linux 2.6.23.2
On Fri, Nov 16, 2007 at 09:39:58PM +0200, Matti Aarnio wrote:
> On Fri, Nov 16, 2007 at 02:35:29PM -0500, Mark Lord wrote:
> > Greg Kroah-Hartman wrote:
> >> We (the -stable team) are announcing the release of the 2.6.23.2 kernel.
> >> It contains a number of bugfixes for the core kernel code.
> >> I'll also be replying to this message with a copy of the patch between
> >> 2.6.23.1 and 2.6.23.2
> > ..
> >> Tsugikazu Shibata (1):
> >> HOWTO: update ja_JP/HOWTO with latest changes
> > ..
> >
> > So what is the magic command to apply this patch successfully?
> > It keeps rejecting the Documentation/ja_JP/HOWTO updates here.
>
> Hammer GIT coders into sensibility to add proper MIME headers
> on these patch post. Then, perhaps, things will just work.
> (and postmaster won't get tons of rejects..)
GIT was only involved in creating the raw patch, which was then
compressed with gzip, then uncompressed and directly included in vim
into a raw email message when then mutt sent out.
So, if the mime headers were wrong on the patch that I sent out, it is
mutts fault, not git.
If you are trying to apply the patch directly from somewhere else, where
did it come from?
thanks,
greg k-h
-
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