mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Arjan van de Ven <arjan@infradead.org>
To: Jens Axboe <axboe@suse.de>
Cc: Jeff Garzik <jgarzik@pobox.com>,
	Dominik Brodowski <linux@dominikbrodowski.net>,
	Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] pcmcia: add another ide-cs CF card id
Date: Thu, 02 Mar 2006 12:56:42 +0100	[thread overview]
Message-ID: <1141300602.3206.44.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <20060302114220.GH4329@suse.de>

On Thu, 2006-03-02 at 12:42 +0100, Jens Axboe wrote:
> On Thu, Mar 02 2006, Arjan van de Ven wrote:
> > On Thu, 2006-03-02 at 06:17 -0500, Jeff Garzik wrote:
> > > Dominik Brodowski wrote:
> > > > On Wed, Mar 01, 2006 at 06:36:17PM -0500, Jeff Garzik wrote:
> > > >>Linux Kernel Mailing List wrote:
> > > >>>commit 42935656914b813c99f91cbac421fe677a6f34ab
> > > >>>tree d37a0d20998f4d87a4bd014300f707c3852ef5f9
> > > >>>parent 82d56e6d2e616bee0e712330bad06b634f007a46
> > > >>>author David Brownell <david-b@pacbell.net> Wed, 25 Jan 2006 22:36:32 -0800
> > > >>>committer Dominik Brodowski <linux@dominikbrodowski.net> Wed, 01 Mar 2006 
> > > 
> > > >>Why was this not CC'd to the IDE maintainer, and linux-ide?
> > > 
> > > > For it is trivial, PCMCIA-related and my time is very limited these days.
> > > 
> > > That's pathetic.  You couldn't even CC linux-kernel on your answer.  And 
> > > this is not even the first or second time you've been asked to CC a 
> > > maintainer.
> > 
> > I personally don't consider that maintainers have a right to demand
> > CC's. Sure it's polite and good to CC them, but that's not the same as
> > having the right to demand this.
> 
> How do you expect the patch to be picked up, if you don't cc the
> maintainer? 

in this case brodo IS the ide-cs maintainer arguably ;)

but if you do a kernel wide change (say add a parameter to a function)
being forced to look up 5000 different maintainers is nonsense.
sure sending it to lkml and some bigger lists is good for that, but
still.


  reply	other threads:[~2006-03-02 11:56 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200603012259.k21MxBXC013582@hera.kernel.org>
2006-03-01 23:36 ` Jeff Garzik
     [not found]   ` <20060302075004.GA17789@isilmar.linta.de>
2006-03-02 11:17     ` Jeff Garzik
2006-03-02 11:31       ` Arjan van de Ven
2006-03-02 11:42         ` Jens Axboe
2006-03-02 11:56           ` Arjan van de Ven [this message]
2006-03-02 12:07           ` Arjan van de Ven
2006-03-02 12:15             ` Jeff Garzik
2006-03-02 12:24               ` Russell King
2006-03-02 12:38                 ` Jeff Garzik
2006-03-02 13:02                   ` Arjan van de Ven
2006-03-02 12:27               ` Arjan van de Ven
2006-03-02 12:40                 ` Jeff Garzik
2006-03-02 13:00               ` Dominik Brodowski
2006-03-02 13:06                 ` Jeff Garzik
2006-03-02 11:44         ` Jeff Garzik

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=1141300602.3206.44.camel@laptopd505.fenrus.org \
    --to=arjan@infradead.org \
    --cc=axboe@suse.de \
    --cc=jgarzik@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@dominikbrodowski.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

all inboxes | Powered by JetHome®