From: Al Viro <viro@ZenIV.linux.org.uk>
To: Philipp Riemer <ruderphilipp@gmail.com>
Cc: Joe Perches <joe@perches.com>,
Greg KH <gregkh@linuxfoundation.org>,
Jiri Kosina <jkosina@suse.cz>, Paul Mundt <lethal@linux-sh.org>,
Michael B?sch <m@bues.ch>,
Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
Uwe Kleine-K?nig <u.kleine-koenig@pengutronix.de>,
LKML <linux-kernel@vger.kernel.org>,
Wang Chen <ellre923@gmail.com>, Jonathan Corbet <corbet@lwn.net>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [GIT PULL] new mailmap file for the linux kernel git repository
Date: Fri, 1 Jun 2012 17:45:18 +0100 [thread overview]
Message-ID: <20120601164518.GI30000@ZenIV.linux.org.uk> (raw)
In-Reply-To: <CAFU-uVupiK5O-LC=wA3Tte78hjzwSJSwUGLb2-58VJSs5z0_hQ@mail.gmail.com>
On Fri, Jun 01, 2012 at 10:41:06AM +0200, Philipp Riemer wrote:
> Does your comment in parentheses mean that your "ftp.linux.org.uk" and
> "www.linux.org.uk" addresses
> (c|sh)ould be mapped onto "zeniv.linux.org.uk"?
ftp.linux.org.uk and zeniv.linux.org.uk are the same box; both variants
will work, but I prefer to use the latter in signoffs, etc.
www.linux.org.uk is an unrelated system and I have no idea if it'll
forward the mail sent to viro@... over to zeniv. No reason for it
to do so...
> If no-one would care about correct name mappings, why does the
> .mailmap file in Git exist at all?
No idea.
> Or websites like Linux Kernel Patch
> Statistic
> <http://www.remword.com/kps_result/>?
Because people are prone to masturbation? "Nation by line", my arse...
What next? Number and ages of children[1]? What a sad bunch of wankers...
[1] which probably _is_ a significant factor, unlike citizenship/nationality/
whatever the hell they meant there.
next prev parent reply other threads:[~2012-06-01 16:45 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-16 14:25 [GIT PULL] new mailmap file for the linux kernel git repository Philipp Riemer
2012-05-16 14:38 ` Greg KH
2012-05-16 14:41 ` Jiri Kosina
2012-05-16 15:01 ` Philipp Riemer
2012-05-16 15:08 ` Greg KH
2012-05-16 15:21 ` Philipp Riemer
2012-05-31 16:08 ` Philipp Riemer
2012-05-31 19:25 ` Joe Perches
2012-05-31 20:15 ` Al Viro
2012-06-01 8:41 ` Philipp Riemer
2012-06-01 11:41 ` Alan Cox
2012-06-01 16:45 ` Al Viro [this message]
2012-06-01 15:16 ` Philipp Riemer
2012-06-28 5:21 ` Joe Perches
2012-06-28 9:00 ` Philipp Riemer
[not found] ` <CAD6jFUQAUAqSz3vAmQtvPFBQZC82DJ4dD9TdRs37DHTZjNUuOQ@mail.gmail.com>
[not found] ` <CAFU-uVs2i8Sf7CqUvndyo8-TUNH4CYjXzu4KXPhLvLo-JLcuWQ@mail.gmail.com>
2012-08-10 13:39 ` [PATCH] " Philipp Riemer
2012-06-01 7:58 ` [GIT PULL] " Greg KH
2012-06-01 16:22 ` Philipp Riemer
2012-06-01 16:23 ` Philipp Riemer
2012-05-16 16:10 ` Joe Perches
2012-05-16 16:46 ` Philipp Riemer
2012-05-16 16:49 ` Josh Boyer
2012-05-16 17:01 ` Philipp Riemer
2012-05-16 17:58 ` Greg KH
2012-05-16 16:52 ` Joe Perches
2012-06-04 6:28 ` Geert Uytterhoeven
2012-06-04 8:42 ` Philipp Riemer
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=20120601164518.GI30000@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=corbet@lwn.net \
--cc=ellre923@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jkosina@suse.cz \
--cc=joe@perches.com \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=lethal@linux-sh.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m@bues.ch \
--cc=ruderphilipp@gmail.com \
--cc=torvalds@linux-foundation.org \
--cc=u.kleine-koenig@pengutronix.de \
/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