public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Jeff Garzik <jeff@garzik.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: remove broken URLs from net drivers' output
Date: Thu, 10 May 2007 06:58:31 +0200	[thread overview]
Message-ID: <20070510045831.GH23574@stusta.de> (raw)
In-Reply-To: <46429E59.1050505@garzik.org>

On Thu, May 10, 2007 at 12:23:53AM -0400, Jeff Garzik wrote:
> Adrian Bunk wrote:
>> It had been sent twice to both linux-kernel and netdev, and when going 
>> through old linux-kernel emails I considered it trivial enough (people 
>> might argue about dead email addresses, but not about dead URLs).
>> I could send such patches to Andrew for that he includes them in -mm and 
>> therefore will include them in his huge list of "forward again and again 
>> to the maintainer until there is any reaction" patches.
>> But IMHO for such trivial patches it's enough if the maintainer had the 
>> chance to veto them.
>
>
> Please follow the rule that everybody else follows:  send to me and netdev. 
>  It's that simple :)

This doesn't answer the main question:
How often, if there's no maintainer reaction?

It happens that Andrew forwards patches from me in -mm 5 or 10 times to 
a maintainer until he gets any reaction from the maintainer.

Before I'd start the same with trivial patches, it would be easier to 
change the "trivial@kernel.org" mail alias to point to Andrew so that 
trivial patches can also become part of his "forward patches to 
maintainers again and again until there's any reaction" process.

That's not meant as a threat or anything like that, it's a serious 
suggestion to avoid duplicated work.

> 	Jeff

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


      reply	other threads:[~2007-05-10  4:58 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200705092102.l49L2Re6028694@hera.kernel.org>
2007-05-09 22:41 ` remove broken URLs from net drivers' output Jeff Garzik
2007-05-09 23:04   ` Jesper Juhl
2007-05-10  4:07     ` Adrian Bunk
2007-05-10  4:22       ` Jeff Garzik
2007-05-10  4:47         ` Adrian Bunk
2007-05-10  9:44           ` Jesper Juhl
2007-05-10  3:57   ` Adrian Bunk
2007-05-10  4:23     ` Jeff Garzik
2007-05-10  4:58       ` Adrian Bunk [this message]

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=20070510045831.GH23574@stusta.de \
    --to=bunk@stusta.de \
    --cc=akpm@linux-foundation.org \
    --cc=jeff@garzik.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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