mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Harvey Harrison <harvey.harrison@gmail.com>,
	Mauro Carvalho Chehab <mchehab@infradead.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: If you want me to quit I will quit
Date: Sat, 26 Apr 2008 17:44:04 +0300	[thread overview]
Message-ID: <20080426144404.GG2252@cs181133002.pp.htv.fi> (raw)
In-Reply-To: <20080426112717.GA23248@uranus.ravnborg.org>

On Sat, Apr 26, 2008 at 01:27:17PM +0200, Sam Ravnborg wrote:
> Hi Adrian.

Hi Sam,

> > Why do other people get over 100 checkpatch fixes into the tree at once 
> > or Linus applies patches directly bypassing the maintainers (like the 
> > one you sent just before [3], which I've also already sent before [4]) 
> > but my patches bitrot forever?
> 
> The patches you submit touches all parts of the kernel tree.
> And you do a good job in finding the relevant receivers.
> 
> To me you are partly in the saem situation as Andrew in that
> you handle a great deal of patches touching a lot of different
> subsystems.
>...

Linus takes patches from people like Andrew, Al and Harvey directly,
but he doesn't take the same patches directly from me.

Whatever applies to these people doesn't help me.

> So in your position I would keep all patches in
> a place so they can be sucked into -next and regular spam
> the relevant amintainers with their patches.
> When the merge window opens then submit the rest to Linus
> with a noe that they have been sent to Maintainers without
> any feedback previously.
> 
> This is not far away from what you do now and should not create
> that big frustrations (I hope).

You missed the "And Linus didn't even bother to answer what the correct 
path for my patches is."

I'd have no problem creating a git tree for such stuff.

But if Linus doesn't bother to tell me how he wants to get patches from 
me he most likely also won't bother to pull from my tree.


And it wouldn't be usable for bugfixes that should get into 2.6.26.

It might e.g. make sense to let maintainers handle fixes and let them 
decide whether they want a patch this way, but if my patch goes through 
the maintainer and later Linus applies the same patch by someone else 
directly it simply makes no sense that I spend my spare time on fixing 
bugs in the kernel.


> 	Sam

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:[~2008-04-26 14:44 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-26  6:14 [BUILDFIX PATCH] au0828: debug is a poor global identifier Harvey Harrison
2008-04-26 11:00 ` If you want me to quit I will quit Adrian Bunk
2008-04-26 11:27   ` Sam Ravnborg
2008-04-26 14:44     ` Adrian Bunk [this message]
2008-04-26 16:51       ` Linus Torvalds
2008-04-26 17:09         ` Adrian Bunk
2008-04-26 17:21           ` Linus Torvalds
2008-04-26 17:35             ` Adrian Bunk
2008-04-26 17:56               ` Linus Torvalds
2008-04-26 14:51   ` Andrew Morton
2008-04-26 15:23     ` Adrian Bunk
2008-04-26 15:44       ` Andrew Morton
2008-04-26 17:16         ` Adrian Bunk
2008-04-26 17:20           ` Andrew Morton
2008-04-26 17:27             ` Adrian Bunk
2008-04-26 17:35               ` Linus Torvalds
2008-04-26 17:31           ` Linus Torvalds
2008-04-26 17:42             ` Sam Ravnborg
2008-04-26 18:26               ` Linus Torvalds
2008-04-26 18:51             ` Stefan Richter
2008-04-26 19:05               ` Linus Torvalds
2008-04-26 19:18                 ` Linus Torvalds
2008-04-26 20:30                   ` Andrew Morton
2008-04-26 20:35                     ` Linus Torvalds
2008-04-28 19:05                       ` Romano Giannetti
2008-04-26 20:49                     ` Stefan Richter
2008-04-27 12:07                     ` Richard Purdie
2008-04-27 14:28                       ` Stefan Richter
2008-04-26 19:43                 ` Stefan Richter
2008-04-27  0:31             ` David Miller
2008-04-27  2:58               ` Jeff Garzik
2008-04-27 16:09             ` Ingo Molnar
2008-04-26 16:21   ` Bartlomiej Zolnierkiewicz
2008-04-26 17:10   ` Adrian Bunk
2008-04-26 19:20   ` Harvey Harrison
2008-04-26 19:42     ` Adrian Bunk

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=20080426144404.GG2252@cs181133002.pp.htv.fi \
    --to=bunk@stusta.de \
    --cc=harvey.harrison@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mchehab@infradead.org \
    --cc=sam@ravnborg.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

all inboxes | Powered by JetHome®