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 18:23:41 +0300
From:	Adrian Bunk <bunk@...nel.org>
To:	Andrew Morton <akpm@...ux-foundation.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 07:51:32AM -0700, Andrew Morton wrote:
> On Sat, 26 Apr 2008 14:00:44 +0300 Adrian Bunk <bunk@...nel.org> wrote:
> 
> > 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?
> 
> If I am not cc'ed on a patch and have to resort to plucking it off the
> mailing list it ends up being significantly more work and more error-prone
> for me to process it.
> 
> I used to merge your patches but then you chose to stop ccing me on them so
> I stopped applying them.  The increased hassle just isn't worth it for some
> random make-foo-static patch.  I do try to keep an eye out for more
> significant changes but hey, stuff happens.
> 
> You chose to disrupt the workflow and now you're here complaining and blaming
> others for the consequences of your own action.


Why didn't you tell me an explicit Cc is important for you?

I'll resend my pending batch with a Cc to you.


That only leaves the question why bugfixes are directly applied by Linux 
when they come from other people, but not when they come from me. Is 
there also a Cc required? But my patch for the x86 userspace headers 
fuckup was Cc'ed to Linus (and I can't send it to -stable before it is 
in Linus' tree).

Is the correct path for bug fixes to go through the maintainer or to go 
directly through Linus? And in the latter case, what was wrong with my 
patches?


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/