From: David Woodhouse <dwmw2@infradead.org>
To: Russell King <rmk+lkml@arm.linux.org.uk>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
torvalds@osdl.org
Subject: Re: When we detect that a 16550 was in fact part of a NatSemi SuperIO chip
Date: Sun, 22 May 2005 14:23:23 +0100 [thread overview]
Message-ID: <1116768204.19183.44.camel@localhost.localdomain> (raw)
In-Reply-To: <20050522135943.E12146@flint.arm.linux.org.uk>
On Sun, 2005-05-22 at 13:59 +0100, Russell King wrote:
> Until then, your opinions are only opinions and I don't have to take
> any notice what so ever of you.
You're right that my opinions are irrelevant.
However, if you are right in thinking that you're affected by the DPA,
then my request as a 'data subject' that you correct your copy of my
personal information would be entirely relevant, and you would be
legally obliged to obey.
> It's rather a shame that you can't be patient and work this out in
> a civilised manner isn't it?
Russell, you took a patch which I had Cc'd to you merely as a courtesy,
mangled the attribution and passed it on, despite the fact that I had
previously asked you not to do so.
When I asked you again not to do that, you were abusive. I'm sorry if
you feel that asking Linus not to apply such things isn't civilised --
but I did ask you politely first, only to receive an abusive reply:
<dwmw2_gone> rmk: I know your policy and that's why I sent the patch to
akpm instead of to you. I Cc'd you as a courtesy. Yet you still
mangled the attribution and sent my patch on.
<dwmw2_gone> So... are you going to refrain from doing that in future,
or am I going to stop Ccing you?
<rmk> dwmw2: oh fuck you, sorry. I'm really not in the mood for your
bloody mindedness.
All you needed to say was "OK, then I won't apply your patches".
--
dwmw2
next prev parent reply other threads:[~2005-05-22 13:26 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200505220008.j4M08uE9025378@hera.kernel.org>
2005-05-22 11:57 ` When we detect that a 16550 was in fact part of a NatSemi SuperIO chip David Woodhouse
2005-05-22 12:59 ` Russell King
2005-05-22 13:23 ` David Woodhouse [this message]
2005-05-22 13:41 ` Russell King
2005-05-22 14:14 ` David Woodhouse
2005-05-22 21:16 ` Alan Cox
2005-05-22 21:50 ` Linus Torvalds
2005-05-22 22:22 ` Alan Cox
2005-05-22 22:40 ` Linus Torvalds
2005-05-22 22:43 ` Alan Cox
2005-05-23 4:09 ` Willy Tarreau
2005-05-23 5:15 ` Dmitry Torokhov
2005-05-23 7:21 ` Willy Tarreau
2005-05-23 14:27 ` Linus Torvalds
2005-05-22 16:59 ` Linus Torvalds
2005-05-22 17:15 ` David Woodhouse
2005-05-22 18:14 ` Arjan van de Ven
2005-05-22 18:44 ` Russell King
2005-05-22 18:51 ` Arjan van de Ven
2005-05-22 19:03 ` Russell King
2005-05-22 20:31 ` Linus Torvalds
2005-05-22 20:55 ` Brian O'Mahoney
2005-05-22 19:58 ` Brian O'Mahoney
2005-05-22 20:31 ` Lee Revell
2005-05-22 20:48 ` Linus Torvalds
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=1116768204.19183.44.camel@localhost.localdomain \
--to=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk+lkml@arm.linux.org.uk \
--cc=torvalds@osdl.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