From: Benjamin Herrenschmidt <bh40@calva.net>
To: Paul Mackerras <paulus@linuxcare.com>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: 2.2.13 build OOB?; need for some standardization here?
Date: Wed, 29 Sep 1999 10:58:02 +0200 [thread overview]
Message-ID: <19990929105802.005899@mailhost.mipsys.com> (raw)
In-Reply-To: <99092914301001.09002@argo.anu.edu.au>
On Wed, Sep 29, 1999, Paul Mackerras <paulus@linuxcare.com> wrote:
>I hope to set up an ftp server shortly where I will be able to
>distribute kernels without the restrictions that I have on
>ftp.samba.org. It will probably be ftp.ozlabs.linuxcare.com or
>something like that.
Hi Paul, glad to hear from you again ;)
My 2 cents: could you make, on this server, some kind of "cleaning room"
for patches ? There are more and more patches floating around to fix
small details (yet another sound fix, a mouse fix, my own little fixes
here or there, etc...) which are quite scattered. I know Cort made
somthing similar on linuxppc.cs.nmt.edu, I don't know if it still exist
however. (I've been away from linuxppc dev. for some time too, I'm back
hacking only since we did that sleep stuff).
Regards,
Benjamin.
--
Perso. e-mail: <mailto:bh40@calva.net>
Work e-mail: <mailto:benh@mipsys.com>
BenH. Web : <http://calvaweb.calvacom.fr/bh40/>
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next parent reply other threads:[~1999-09-29 8:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <99092914301001.09002@argo.anu.edu.au>
1999-09-29 8:58 ` Benjamin Herrenschmidt [this message]
1999-09-28 18:08 2.2.13 build OOB?; need for some standardization here? Kevin_Hendricks
1999-09-28 18:39 ` David Edelsohn
1999-09-30 18:04 ` Michel Lanners
-- strict thread matches above, loose matches on Subject: below --
1999-09-28 15:20 Kevin_Hendricks
1999-09-28 16:15 ` Sriranga Veeraraghavan
1999-09-28 16:48 ` Geert Uytterhoeven
1999-09-28 17:27 ` Sriranga Veeraraghavan
1999-09-28 17:45 ` Hollis R Blanchard
1999-09-28 20:34 ` Deirdre Saoirse
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=19990929105802.005899@mailhost.mipsys.com \
--to=bh40@calva.net \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=paulus@linuxcare.com \
/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).