linux-kernel - Re: Preempt-RT patch for 2.6.25

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]

Date:	Tue, 6 May 2008 10:43:38 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Daniel Walker <dwalker@...sta.com>
Cc:	Thomas Gleixner <tglx@...utronix.de>,
	Steven Rostedt <rostedt@...dmis.org>,
	Sven-Thorsten Dietrich <sven@...bigcorporation.com>,
	Remy Bohmer <linux@...mer.net>,
	LKML <linux-kernel@...r.kernel.org>,
	RT <linux-rt-users@...r.kernel.org>,
	Jon Masters <jonathan@...masters.org>
Subject: Re: Preempt-RT patch for 2.6.25

* Daniel Walker <dwalker@...sta.com> wrote:

> > Since it's code that you regard stale it shouldnt be all that hard 
> > to fix it up - in general it's much easier to fix a bug than to talk 
> > it out of existence, even if you disagree with a maintainer about 
> > how significant a bug is.
> 
> It shouldn't be hard, but it's too much to do all in one go. [...]

this sort of "it was too hard for me but I expect the maintainers to 
clean up the mess" stance, combined with an aggressive, uncompromising, 
demanding tone towards the maintainers of a project wont get you very 
far in contributing to any open-source project. You are not their boss, 
you have to learn to work with them instead of trying to force your 
opinion on them. They clearly try to work with you and gave a 
straightforward technical description of how your contribution would be 
acceptable to the project. All the rest is just a waste of everyone's 
time that could be better spent on improving the project. JFYI.

	Ingo
--
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/