From: David Woodhouse <dwmw2@infradead.org>
To: Josh Boyer <jwboyer@linux.vnet.ibm.com>
Cc: linuxppc-dev@ozlabs.org, paulus@samba.org
Subject: Re: [PATCH] Schedule removal of arch/ppc
Date: Fri, 29 Jun 2007 16:14:42 +0100 [thread overview]
Message-ID: <1183130082.1170.344.camel@pmac.infradead.org> (raw)
In-Reply-To: <1183130011.30145.35.camel@weaponx.rchland.ibm.com>
On Fri, 2007-06-29 at 10:13 -0500, Josh Boyer wrote:
> That's it? I'm scheduling the demise of an entire architecture
> sub-tree and the only comment you can make is about a superfluous
> apostrophe? ;)
Sorry, allow me to rephrase...
http://www.angryflower.com/itsits.gif
DIE arch/ppc DIE!
--
dwmw2
next prev parent reply other threads:[~2007-06-29 15:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-27 13:49 [PATCH] Schedule removal of arch/ppc Josh Boyer
2007-06-29 14:54 ` David Woodhouse
2007-06-29 15:13 ` Josh Boyer
2007-06-29 15:14 ` David Woodhouse [this message]
2007-06-29 17:23 ` Mark A. Greer
2007-06-29 16:05 ` Segher Boessenkool
2007-06-30 7:58 ` Michael Ellerman
2007-06-30 8:18 ` David Woodhouse
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=1183130082.1170.344.camel@pmac.infradead.org \
--to=dwmw2@infradead.org \
--cc=jwboyer@linux.vnet.ibm.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.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).