linux-kernel - Re: [PATCH] Re: linux-2.6.19-rc5-g088406bc build #120 failed

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: <4558E652.1080905@microgate.com>
Date:	Mon, 13 Nov 2006 15:40:34 -0600
From:	Paul Fulghum <paulkf@...rogate.com>
To:	Krzysztof Halasa <khc@...waw.pl>
CC:	Jeff Garzik <jeff@...zik.org>,
	Toralf Förster <toralf.foerster@....de>,
	linux-kernel@...r.kernel.org, Andrew Morton <akpm@...l.org>
Subject: Re: [PATCH] Re: linux-2.6.19-rc5-g088406bc build #120 failed

Krzysztof Halasa wrote:
>>We were in a perpetual state of:
>>
>>1. supply patch
>>2. get criticism from new person just joining thread
>>3. change patch to address criticism
>>4. goto #1
> 
> 
> Right, the description fits. OTOH I recall the criticism had a fair
> amount of merit. That's how the things work here. Been there many
> times BTW.

To be more precise, that is many distinct
criticisms from distinct people, some of which
contradict each other.

I know code is open to criticism,
but after several weeks of submitting patches
and getting no closer to acceptance I gave up.
We were going around in circles where one person
wanted some thing that conflicted with what
another person wanted.

>>But since we seem stuck in a state where real fixes
>>are not allowed, and this breakage is constantly reintroduced,
> 
> It may look like that sometimes but it's not real. Anyway I think
> everyone would benefit from the correct fix and the issue wouldn't
> come again. Having looked at it I'd fix it myself but I'm pretty
> sure you still have the old patch (which changes CONFIG_ macros
> outside Kconfig, I mean in .c files) and it could be trivially
> modified then applied (and perhaps tested with real hardware if
> needed).

There isn't much point in resubmitting the previously
rejected patches only to be rejected again.

I was planning on trying again in a month or two
to see if all the people who rejected all of the
previous patches have come to some sort of agreement.

Without such agreement we are left in the state
of never ending patches.

-- 
Paul Fulghum
Microgate Systems, Ltd.
-
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/