linux-kernel - Re: If you want me to quit I will quit

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sat, 26 Apr 2008 17:44:04 +0300
From:	Adrian Bunk <bunk@...sta.de>
To:	Sam Ravnborg <sam@...nborg.org>
Cc:	Harvey Harrison <harvey.harrison@...il.com>,
	Mauro Carvalho Chehab <mchehab@...radead.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: If you want me to quit I will quit

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

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/