From: Matthew Wilcox <matthew@wil.cx>
To: linux-ia64@vger.kernel.org
Subject: Re: git-nfsd on ia64
Date: Sun, 17 Feb 2008 14:08:21 +0000 [thread overview]
Message-ID: <20080217140821.GA21012@parisc-linux.org> (raw)
In-Reply-To: <20080215223943.d12b8eb5.akpm@linux-foundation.org>
On Sun, Feb 17, 2008 at 08:21:32AM -0500, Christoph Hellwig wrote:
> That implies maintainers actually maintaining it. When did we get the
> last real update (nto just removeing dead options) to the 32bit x86
> defconfig?
The last one I recall was in July 2006 when someone set the SUSPEND
partition in defconfig and machines without that partition existing
would panic on bootup.
--
Intel are signing my paycheques ... these opinions are still mine
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours. We can't possibly take such
a retrograde step."
prev parent reply other threads:[~2008-02-17 14:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-16 6:39 git-nfsd on ia64 Andrew Morton
2008-02-16 6:43 ` Andrew Morton
2008-02-17 1:12 ` J. Bruce Fields
2008-02-17 1:18 ` Andrew Morton
2008-02-17 1:27 ` J. Bruce Fields
2008-02-17 13:13 ` Christoph Hellwig
2008-02-17 13:21 ` Christoph Hellwig
2008-02-17 14:08 ` Matthew Wilcox [this message]
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=20080217140821.GA21012@parisc-linux.org \
--to=matthew@wil.cx \
--cc=linux-ia64@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