From: Steven Cole <elenstev@mesatop.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Andrew Morton <akpm@osdl.org>,
mfedyk@matchmail.com, superchkn@sbcglobal.net,
solt@dns.toxicfilms.tv, linux-kernel@vger.kernel.org,
webmaster@kernel.org
Subject: Re: -mm patches on www.kernel.org ?
Date: 01 Sep 2003 21:40:20 -0600 [thread overview]
Message-ID: <1062474020.3477.16.camel@spc> (raw)
In-Reply-To: <3F53E3AB.7070604@zytor.com>
On Mon, 2003-09-01 at 18:26, H. Peter Anvin wrote:
> Andrew Morton wrote:
>
> >
> > Well I always have a full rollup there, such as
> >
> > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.0-test4/2.6.0-test4-mm4/2.6.0-test4-mm4.gz
> >
> > Is that what you mean?
> >
> > (It would be good to add -aa patchsets too).
> >
>
> I might be able to do this. However, please understand, everyone, that
> having to write individual scripts for each kernel author is turning
> into a horrible pain in the ass. I think the only sane way to do this
> is to come up with a standard directory layout for specific user patches.
>
> -hpa
Or you could just post a few example scripts, along with a few more
comments about how hard this is.
Then you can watch your fence get whitewashed for free.
Steven
next prev parent reply other threads:[~2003-09-02 3:41 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-01 14:05 Maciej Soltysiak
2003-09-01 21:11 ` Mike Fedyk
2003-09-01 21:42 ` Wes Janzen
[not found] ` <3F53B937.10103@sbcglobal.net>
2003-09-01 22:53 ` Mike Fedyk
2003-09-02 0:05 ` H. Peter Anvin
2003-09-02 0:13 ` CaT
2003-09-02 0:14 ` Andrew Morton
2003-09-02 0:26 ` H. Peter Anvin
2003-09-02 3:40 ` Steven Cole [this message]
2003-09-02 3:44 ` H. Peter Anvin
2003-09-02 0:28 ` Matt Heler
2003-09-02 0:33 ` Mike Fedyk
2003-09-02 10:28 ` Maciej Soltysiak
2003-09-02 0:43 ` Robert Love
2003-09-02 1:30 ` Matt Heler
2003-09-02 1:54 ` Zwane Mwaikambo
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=1062474020.3477.16.camel@spc \
--to=elenstev@mesatop.com \
--cc=akpm@osdl.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mfedyk@matchmail.com \
--cc=solt@dns.toxicfilms.tv \
--cc=superchkn@sbcglobal.net \
--cc=webmaster@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
all inboxes | Powered by JetHome®