From: Mr Dash Four <mr.dash.four@googlemail.com>
To: Mr Dash Four <mr.dash.four@googlemail.com>,
David Miller <davem@davemloft.net>,
stephen@networkplumber.org, netdev@vger.kernel.org
Subject: Re: [PATCH] iproute2: lib/utils.c bug fixes
Date: Fri, 12 Apr 2013 19:36:38 +0100 [thread overview]
Message-ID: <51685436.7000407@googlemail.com> (raw)
In-Reply-To: <20130412181850.GB30292@order.stressinduktion.org>
Hannes Frederic Sowa wrote:
> On Fri, Apr 12, 2013 at 06:58:40PM +0100, Mr Dash Four wrote:
>
>> David Miller wrote:
>>
>>> The self-rightousness with which people operating under pseudonyms or
>>> names that do not meet the requirements of the developers certificate
>>> of origin react when they are confronted directly about this issue I
>>> find truly appalling.
>>>
>>>
>> I assume this was aimed at me, in which case I'll ask again - on what
>> basis you or Stephen have determined that I do not comply with these
>> terms (this is a genuine question, not a wind up - just in case you or
>> anybody else start making assumptions!)?
>>
>
> Please don't play a cat and mouse game with the folks around here. Is your
> submission signed off with your *real* name?
*Yes* - I thought that was pretty obvious.
Stephen determined that for whatever reason the name appearing in the
Signed-By tag "is a bit strange", so it must either be made up or a
pseudonym and I took issue with this.
> This is a simple requirement for patch submissions.
Which is fair enough, I suppose.
> Why do you let the people reviewing and perhaps committing
> your patch guess? Just clarify it in one sentence.
I am not sure I understand that question, but my patch submission is
simply to correct 3 bugs in the current iproute2 tree - there is no
other (ulterior) motive behind it. I am letting people reviewing (or
committing) that patch as they are the (current/rightful) maintainers of
this project (iproute2). This (the reason for issuing the patch and the
subsequent request to review it) was made, I think pretty clear, in the
patch submission heading.
> If it is not your real name it does violate the policy. It is that simple.
>
I was perfectly aware of that before making that submission - as I
already pointed out in one of my previous posts, this isn't my first
submission (in the kernel tree as well as in other open-source projects)
and I hope it won't be the last.
next prev parent reply other threads:[~2013-04-12 18:36 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-12 2:30 [PATCH] iproute2: lib/utils.c bug fixes Mr Dash Four
2013-04-12 3:06 ` Stephen Hemminger
2013-04-12 13:49 ` Mr Dash Four
2013-04-12 14:25 ` Eric Dumazet
2013-04-12 14:38 ` Mr Dash Four
2013-04-12 15:09 ` Eric Dumazet
2013-04-12 15:25 ` Mr Dash Four
2013-04-12 15:45 ` Eric Dumazet
2013-04-12 16:15 ` Mr Dash Four
2013-04-12 16:21 ` Bjørn Mork
2013-04-12 16:02 ` Stephen Hemminger
2013-04-12 16:16 ` Mr Dash Four
2013-04-12 17:36 ` David Miller
2013-04-12 17:58 ` Mr Dash Four
2013-04-12 18:15 ` David Miller
2013-04-12 18:18 ` Hannes Frederic Sowa
2013-04-12 18:36 ` Mr Dash Four [this message]
2013-04-12 20:36 ` Hannes Frederic Sowa
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=51685436.7000407@googlemail.com \
--to=mr.dash.four@googlemail.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.