From: Guenter Roeck <linux@roeck-us.net>
To: Li Zefan <lizefan@huawei.com>
Cc: stable@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [kernel.org PATCH] Li Zefan is now the 3.4 stable maintainer
Date: Thu, 4 Sep 2014 11:39:53 -0700 [thread overview]
Message-ID: <20140904183953.GA28599@roeck-us.net> (raw)
In-Reply-To: <540813A5.7020704@huawei.com>
On Thu, Sep 04, 2014 at 03:24:21PM +0800, Li Zefan wrote:
> Hi Guenter,
>
> Sorry for my late reply.
>
> On 2014/8/27 12:59, Guenter Roeck wrote:
> > On Tue, Aug 26, 2014 at 04:08:58PM -0700, Greg KH wrote:
> >> Li has agreed to continue to support the 3.4 stable kernel tree until
> >> September 2016. Update the releases.html page on kernel.org to reflect
> >> this.
> >>
> > Li,
> >
> > it would be great if you can send me information about your -stable queue,
> > ie how you maintain it and where it is located. This will enable me to
> > continue testing the stable queue for the 3.4 kernel.
> >
>
> Thanks for testing LTS kernels!
>
> This is my 3.4.y git tree:
>
> https://git.kernel.org/cgit/linux/kernel/git/lizf/linux-3.4.y.git/
>
> And this is the patch queue:
>
> https://git.kernel.org/cgit/linux/kernel/git/lizf/linux-3.4.y-queue.git/
>
> I use quilt. When I've added some patches to 3.4.y, I'll update this
> queue. The patches and series file are under /patches. Currently there's
> already a patch in the queue.
>
> When I release a new version, I'll clean up the queue by removing all
> the files under /patches.
>
> Hope this is all the information you need. Please tell me if you need
> me to slightly adjust my workflow so it's easier for you.
It almost works.
Problem is that the pending patch got converted to use <cr><lf> instead of
just <lf> as common in Linux. When I try to apply it with "git quiltimport",
it bails out with "trailing whitespace" errors. "git am" with the individual
patch works fine for some reason, though.
I can try to find a workaround, but it would be better to have the file in
linux file format to start with. Would that be possible ?
Alternatively, does anyone know how to apply files in DOS format (lines
terminated with cr/lf) using quiltimport ?
Thanks,
Guenter
next prev parent reply other threads:[~2014-09-04 18:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-26 23:08 [kernel.org PATCH] Li Zefan is now the 3.4 stable maintainer Greg KH
2014-08-26 23:20 ` Konstantin Ryabitsev
2014-08-27 0:12 ` Josh Boyer
2014-08-27 4:59 ` Guenter Roeck
2014-09-04 7:24 ` Li Zefan
2014-09-04 18:39 ` Guenter Roeck [this message]
2014-09-05 7:55 ` Li Zefan
2014-09-05 13:58 ` Guenter Roeck
2014-09-05 14:24 ` Shuah Khan
2014-09-05 21:49 ` Greg KH
2014-09-05 22:27 ` Guenter Roeck
2014-09-10 2:56 ` Li Zefan
2014-08-27 5:13 ` Willy Tarreau
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140904183953.GA28599@roeck-us.net \
--to=linux@roeck-us.net \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan@huawei.com \
--cc=stable@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).