From: Mr Dash Four <mr.dash.four@googlemail.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: Stephen Hemminger <stephen@networkplumber.org>, netdev@vger.kernel.org
Subject: Re: [PATCH] iproute2: lib/utils.c bug fixes
Date: Fri, 12 Apr 2013 17:15:30 +0100 [thread overview]
Message-ID: <51683322.9060709@googlemail.com> (raw)
In-Reply-To: <1365781557.4459.42.camel@edumazet-glaptop>
Eric Dumazet wrote:
> On Fri, 2013-04-12 at 16:25 +0100, Mr Dash Four wrote:
>
>
>> Now that we cleared this little nugget, can we move along please as the
>> netdev forum isn't the appropriate place to discuss genders, name titles
>> or sexual orientation - something I had no intention of doing (apologies
>> to all who had to put up with this little diversion), but I felt I was
>> dragged into this by your good self and Mr Hemminger. Thank you.
>>
>
> Next time you submit a patch, think about how you can avoid this useless
> discussions by choosing an appropriate signature. (And no, I don't
> suggest you change your name !)
>
Care to enlighten me what your definition of "appropriate signature" is
exactly? I am expecting that your answer would include the appropriate
guidelines used on this mailing list and *not* your personal opinion as,
in this particular case, this is, or should be, irrelevant.
> And this is not a diversion, since I remember you had the same problems
> in the past.
Similar to above - care to point out (in terms of links to previous ML
archives posts and so on) what "problems" did I, allegedly, have had in
the past with patch submissions? Because, to my recollection, I did
*not* have any such problems. If you can't point me to any such
references, then I'd assume that you are simply on a smear trip with an
agenda.
> You perfectly know your signature is not very good, and you
> play with this. I can tell you its not funny.
>
I don't "play" with my signature - I have been using it since I started
contributing to open source projects and that signature never changed.
I would also like to know what do you find that it is "not very good" in
my signature and what particular patch submission guidelines am I
breaking with using it? Again, I am expecting that you will refer to the
relevant guidelines for patch submissions approved on this list when
forming your response and will extricate any personal bias or opinion.
Just to repeat again, so that it is clear - as far as my "signature"
goes, I am not aware of any issues I have allegedly had in the past with
patch submissions, so if you care to point out what these were, please
do so. If not, kindly move on. Thank you.
next prev parent reply other threads:[~2013-04-12 16:15 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 [this message]
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
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=51683322.9060709@googlemail.com \
--to=mr.dash.four@googlemail.com \
--cc=eric.dumazet@gmail.com \
--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 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).