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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20091205.142126.23618243.davem@davemloft.net>
Date:	Sat, 05 Dec 2009 14:21:26 -0800 (PST)
From:	David Miller <davem@...emloft.net>
To:	william.allen.simpson@...il.com
Cc:	joe@...ches.com, brice@...i.com, netdev@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH net-next-2.6] drivers/net: Move && and || to end of
 previous line

From: William Allen Simpson <william.allen.simpson@...il.com>
Date: Sat, 05 Dec 2009 07:43:41 -0500

> These patches should not be accepted to the main Linus tree.

You come out of nowhere as a new contributor.  You have to constantly
ask about policy and other formalities wrt. kernel development.

Yet here you are telling us what should or should not go into the
tree.

You don't even know what the "merge window" is yet you seem so
confident to elicit firm declarations about code policy.

That's nothing but blind arrogance.

Nobody can take you seriously William, really.

And if you think just omitting Joe's patch is going to make your
backporting work any easier, you're mistaken.

Every release we make tons and tons of cleanups and refactorizations
all over the networking and sometimes heavily in TCP.  So you're going
to run into such problems no matter whether Joe's patch goes in or
not.

And like Joe, I think you overstate  how much effort is involved
in such work.  Especially for the size of your patch.

And consider, how in the world do you think it is for me to have to
handle hundreds of patches per day from random people.  If anyone
should get the brunt of the pain, it's me.

Yet I'm ok with it, and you should be too.
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ