From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: "Randy.Dunlap" <rdunlap@xenotime.net>
Cc: "Eric W. Biederman" <ebiederm@xmission.com>,
lkml <linux-kernel@vger.kernel.org>,
drepper@redhat.com, akpm <akpm@osdl.org>,
serue@us.ibm.com, sam@vilain.net, clg@fr.ibm.com, dev@sw.ru
Subject: Re: [PATCH] POSIX-hostname up to 255 characters
Date: Fri, 26 May 2006 20:01:31 +0200 [thread overview]
Message-ID: <20060526180131.GA13513@lug-owl.de> (raw)
In-Reply-To: <Pine.LNX.4.58.0605261025230.9655@shark.he.net>
[-- Attachment #1: Type: text/plain, Size: 1191 bytes --]
On Fri, 2006-05-26 10:28:13 -0700, Randy.Dunlap <rdunlap@xenotime.net> wrote:
> On Fri, 26 May 2006, Jan-Benedict Glaw wrote:
[Patch touchin all archs]
> > ...and this should have gone to linux-arch, too...
>
> so how does someone know:
> (a) that this should have gone to linux-arch
Anything that modifies all architectures (eg. new system calls,
low-level MM changes, ...) should go to linux-arch. This is where all
architecture maintainers are expected to be around.
> (b) that linux-arch exists
Noticing the existance of linux-arch is admittedly a hard job. It's a
quite specialized low-volume list, so most people actually never ever
recognize it--unfortunately.
> (c) what it's full email address it?
The list's email address is linux-arch@vger.kernel.org
> I.e., where is all of this explained?
Nowhere :-/
MfG, JBG
--
Jan-Benedict Glaw jbglaw@lug-owl.de . +49-172-7608481 _ O _
"Eine Freie Meinung in einem Freien Kopf | Gegen Zensur | Gegen Krieg _ _ O
für einen Freien Staat voll Freier Bürger" | im Internet! | im Irak! O O O
ret = do_actions((curr | FREE_SPEECH) & ~(NEW_COPYRIGHT_LAW | DRM | TCPA));
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-05-26 18:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-26 3:45 Randy.Dunlap
2006-05-26 9:14 ` Eric W. Biederman
2006-05-26 14:42 ` Jan-Benedict Glaw
2006-05-26 17:28 ` Randy.Dunlap
2006-05-26 18:01 ` Jan-Benedict Glaw [this message]
2006-05-26 18:15 ` linux-os (Dick Johnson)
2006-05-26 18:28 ` Ulrich Drepper
2006-05-26 18:35 ` linux-os (Dick Johnson)
2006-05-26 18:55 ` Ulrich Drepper
2006-05-26 19:12 ` Jan Engelhardt
2006-05-26 21:31 ` Eric W. Biederman
2006-05-27 1:39 ` Randy.Dunlap
2006-05-27 7:36 ` Randy.Dunlap
2006-05-27 13:54 ` Eric W. Biederman
2006-05-28 18:32 ` Randy.Dunlap
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=20060526180131.GA13513@lug-owl.de \
--to=jbglaw@lug-owl.de \
--cc=akpm@osdl.org \
--cc=clg@fr.ibm.com \
--cc=dev@sw.ru \
--cc=drepper@redhat.com \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@xenotime.net \
--cc=sam@vilain.net \
--cc=serue@us.ibm.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
all inboxes | Powered by JetHome®