From: Jon Maloy <jon.maloy@ericsson.com>
To: Jesper Juhl <jesper.juhl@gmail.com>
Cc: Per Liden <per.liden@ericsson.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Allan Stephens <allan.stephens@windriver.com>,
tipc-discussion@lists.sourceforge.net
Subject: Re: [PATCH] TIPC: add Kconfig help text
Date: Tue, 17 Jan 2006 15:40:08 +0000 [thread overview]
Message-ID: <43CD0FD8.4090003@ericsson.com> (raw)
In-Reply-To: <9a8748490601171238y12be9933ha8068985cf2a1cbf@mail.gmail.com>
That has also been fixed, but not pulled in yet. Same reason as above.
///jon
Jesper Juhl wrote:
>On 1/17/06, Jesper Juhl <jesper.juhl@gmail.com> wrote:
>
>
>>On 1/17/06, Per Liden <per.liden@ericsson.com> wrote:
>>
>>
>>>I've already committed a patch similar to this in our GIT repo
>>>(http://tipc.cslab.ericsson.net), just haven't asked for it to be pulled
>>>yet since we have another fix for some namespace pullution in the
>>>pipeline. Thanks though!
>>>
>>>
>>>
>>Good enough for me :-)
>>
>>
>>
>
>Let me just pick another little nit here.
>
>Your entries in the MAINTAINERS file for TIPC;
>Would it be too much to ask that you list the *correct* email
>addresses for people in there instead of the @nospam.ericsson.com
>obfuscated ones?
>
>As I see it, listing the obfuscated addresses buys you nothing, since
>you are using the real address to post to a public (and widely
>archived) mailing list anyway, and has a few real drawbacks:
>
>- some users (especially users who are not native english speakers)
>may not realize that the "nospam." bit should be taken out and thus
>you may miss emails.
>
>- it adds extra work (small, but still) on everyone who looks up the
>maintainer for TIPC to send you guys emails to parse the addr and
>realize the addr needs to be edited and then actually edit it instead
>of just cut'n'paste.
>
>- it's somewhat annoying.
>
>
>I even opted to send the patch to both the @nospam.ericsson.com and
>@ericsson.com addresses since I didn't know if "nospam." was to be
>taken out or if it was just some subdomain you used specifically for
>communication on public lists that you then did extra SPAM filtering
>on - there's no way to know.
>If you are worried about getting extra SPAM by being listed in
>MAINTAINERS, why don't you just create an extra email alias that you
>list in MAINTAINERS and use for LKML stuff - that alias you can then
>do extra filtering on, dump in a seperate mailbox/folder/whatever... I
>don't think you actually gain anything by your current scheeme.
>
>I'll stop ranting now ;)
>
>--
>Jesper Juhl <jesper.juhl@gmail.com>
>Don't top-post http://www.catb.org/~esr/jargon/html/T/top-post.html
>Plain text mails only, please http://www.expita.com/nomime.html
>
>
next prev parent reply other threads:[~2006-01-17 20:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-17 19:58 [PATCH] TIPC: add Kconfig help text Jesper Juhl
2006-01-17 20:15 ` Per Liden
2006-01-17 20:24 ` Jesper Juhl
2006-01-17 20:38 ` Jesper Juhl
2006-01-17 15:40 ` Jon Maloy [this message]
2006-01-17 20:51 ` Jesper Juhl
2006-01-17 20:38 ` Per Liden
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=43CD0FD8.4090003@ericsson.com \
--to=jon.maloy@ericsson.com \
--cc=allan.stephens@windriver.com \
--cc=jesper.juhl@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=per.liden@ericsson.com \
--cc=tipc-discussion@lists.sourceforge.net \
/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