All of lore.kernel.org
 help / color / mirror / Atom feed
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 15:14:13 +0100	[thread overview]
Message-ID: <1116771254.19183.71.camel@localhost.localdomain> (raw)
In-Reply-To: <20050522144123.F12146@flint.arm.linux.org.uk>

On Sun, 2005-05-22 at 14:41 +0100, Russell King wrote:
> Firstly, I admit to accidentally applying David's patch, which I'm
> sorry for doing.  However, that can't be undone.

Your apology is accepted, but isn't what I was asking for -- and neither
was I asking that you undo it, which obviously isn't possible.

I just wanted to you confirm that you wouldn't do it again. Wasn't that
much clear from the conversation?

You pointed out that I have the right not to send you patches, and I
replied that I was already exercising that right, but I'd merely Cc'd
you on this particular patch as a courtesy. I said "I don't want to have
to stop Cc'ing you when I send patches which you might be interested in.
Please either commit my patches with correct attribution, or don't
commit them at all." 

Your reply didn't include a response to that specific request and seemed
to be disagreeing. So yes, I asked for clarification because I really
don't want to be in a position where I have to refuse to Cc you when
making changes I know you care about...

<dwmw2_gone> rmk: you didn't reply to my last mail. Do you want me to
    continue to Cc you on stuff I think you'll care about?
<rmk> dwmw2: because there's no point in responding any further.
<rmk> dwmw2: certainly not until OSDL provide the results of their
    investigation.
<dwmw2_gone> rmk: I asked a specific question. Are you going to continue
    to take patches on which you were Cc'd merely as a courtesy, mangle 
    the attribution, and send them on?
<dwmw2_gone> If so, I'll refrain from Ccing you in future
<dwmw2_gone> If you are going to either refrain from mangling the
    attribution, or refrain from sending them on in mangled form,
    then that's fine and I'll continue to Cc you. 
<rmk> dwmw2: you know my policy, and I don't see why I should 
    double-standard and open myself up to further flames just because
    your[sic] whinging and being your usual bloody minded self over this.
<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.
* rmk wanders off
<dwmw2_gone> fine. Then don't bitch in future if I change stuff without
    Ccing you

It wasn't an unreasonable request, Russell. I didn't ask you to abandon
your 'policy'; I just asked you not to apply my patches if you insist on
sticking to that policy unconditionally. Again, I'm sorry if you find
that request too onerous or unreasonable. I _could_ relieve you of that
task by just sending patches in without letting you see them -- but as I
said, I'd rather not.

But if I'm really being filed to /dev/null then the question is moot. I
shall simply not bother to Cc you in future when submitting patches I
think you'll care about. The question is therefore answered; thank you.

-- 
dwmw2


  reply	other threads:[~2005-05-22 14:16 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
2005-05-22 13:41     ` Russell King
2005-05-22 14:14       ` David Woodhouse [this message]
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=1116771254.19183.71.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 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.