From: Roman Zippel <zippel@linux-m68k.org>
To: linuxppc-dev@ozlabs.org
Subject: [PATCH 0/8] apus update
Date: Sun, 25 Sep 2005 00:41:23 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.61.0509250032560.19121@scrub.home> (raw)
Hi,
Here are eight patches to get APUS closer to working (actually it was
already enough to get it compiled (after removing BROKEN of course)).
I already sent them over year ago and I updated them to the current state.
It would be nice to apply them this time and forward them to Andrew/Linus
as far as they are acceptable. If you want drop some of it, that's fine,
but I'd like to avoid unnecessary resends.
bye, Roman
next reply other threads:[~2005-09-24 22:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-24 22:41 Roman Zippel [this message]
2005-09-24 23:13 ` [PATCH 0/8] apus update Roman Zippel
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=Pine.LNX.4.61.0509250032560.19121@scrub.home \
--to=zippel@linux-m68k.org \
--cc=linuxppc-dev@ozlabs.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).