LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Martin Schwidefsky <schwidefsky@de.ibm.com>
Cc: Heiko Carstens <heiko.carstens@de.ibm.com>,
Andrew Morton <akpm@linux-foundation.org>,
Greg Kroah-Hartman <gregkh@suse.de>,
linux-kernel@vger.kernel.org, linux-s390@vger.kernel.org
Subject: Re: [GIT PULL/RESEND] kernel message catalog patches
Date: Sun, 26 Oct 2008 12:12:59 -0700 (PDT) [thread overview]
Message-ID: <alpine.LFD.2.00.0810261212290.5200@nehalem.linux-foundation.org> (raw)
In-Reply-To: <1225049195.14057.72.camel@localhost>
On Sun, 26 Oct 2008, Martin Schwidefsky wrote:
>
> > But if it's in-kernel, other people are then going to complain about them
> > not being maintained. And quite frankly, I'm neither willing nor
> > interested in hearing those complaints or making them more "valid".
>
> The usual answer to complaints of this sort is "send a patch", isn't it?
Yes. And why don't you do all that, and not involve me at all, and keep
all of this entirely out of the kernel?
Linus
next prev parent reply other threads:[~2008-10-26 19:14 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-16 14:50 [GIT PULL] " Martin Schwidefsky
2008-10-17 7:59 ` Martin Schwidefsky
2008-10-21 9:21 ` [GIT PULL/RESEND] " Heiko Carstens
2008-10-23 15:35 ` Linus Torvalds
2008-10-23 21:04 ` Heiko Carstens
2008-10-23 21:37 ` Linus Torvalds
2008-10-24 15:50 ` Heiko Carstens
2008-10-26 19:26 ` Martin Schwidefsky
2008-10-26 19:12 ` Linus Torvalds [this message]
2008-10-27 10:01 ` Martin Schwidefsky
2008-10-27 15:05 ` Linus Torvalds
2008-10-27 15:52 ` Martin Schwidefsky
2008-10-27 16:19 ` Theodore Tso
2008-10-27 16:27 ` Randy Dunlap
2008-10-28 8:25 ` Martin Schwidefsky
2008-10-27 16:03 ` Alan Cox
2008-10-27 16:10 ` Linus Torvalds
2008-10-27 16:35 ` Alan Cox
2008-10-27 19:36 ` Theodore Tso
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=alpine.LFD.2.00.0810261212290.5200@nehalem.linux-foundation.org \
--to=torvalds@linux-foundation.org \
--cc=akpm@linux-foundation.org \
--cc=gregkh@suse.de \
--cc=heiko.carstens@de.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=schwidefsky@de.ibm.com \
--subject='Re: [GIT PULL/RESEND] kernel message catalog patches' \
/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
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).