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]
Message-ID: <alpine.DEB.2.00.1009061507180.23167@asgard.lang.hm>
Date:	Mon, 6 Sep 2010 15:14:10 -0700 (PDT)
From:	david@...g.hm
To:	"Nicholas A. Bellinger" <nab@...ux-iscsi.org>
cc:	Vladislav Bolkhovitin <vst@...b.net>,
	James Bottomley <James.Bottomley@...e.de>,
	Dmitry Torokhov <dmitry.torokhov@...il.com>,
	Dirk Meister <dmeister@...-paderborn.de>,
	linux-scsi@...r.kernel.org, Chetan Loke <chetanloke@...il.com>,
	Chetan Loke <generationgnu@...oo.com>,
	scst-devel <scst-devel@...ts.sourceforge.net>,
	linux-kernel@...r.kernel.org, Mike Christie <michaelc@...wisc.edu>,
	FUJITA Tomonori <fujita.tomonori@....ntt.co.jp>
Subject: Re: [Scst-devel] Fwd: Re: linuxcon 2010...

On Mon, 6 Sep 2010, Nicholas A. Bellinger wrote:

> So at this point, I will once again to refrain from any non technical
> interaction with yourself.  If you have geninue concerns about any of
> the TCM/LIO v4 code, then I suggest that you and your devels make them
> known from within threads containing [PATCH] and [RFC] tags, because I
> will not be bothering with anything that does not contain comments on
> creating new or improving existing design and code.

I haven't seen any techinical discussion from you either.

all I see is how your favorite has been blessed as being the next thing to 
be included, even though it still needs work and Vlad's can't even be 
looked at.

that's hardly a technical discussion.

Vlad seems to be trying to document features of the different options, 
naturally he knows his option better than anyone else's. He offered to 
correct his listing with any information provided by anyone else, and 
instead of corrections to the feature lists, we just got accusations of 
handwaving and a reiteration that your favorite was selected in some 
meeting to be merged.

I would like to point out that over the years there have been many things 
that were expected to be merged that didn't get merged. Don't take any 
statement in any meeting to be a final decision. It doesn't matter how 
promising yourcode looked at that point in time, until it's merged you may 
find that it doesn't get merged. And even after it gets merged, if someone 
else has better code, their code may replace yours if the other code is 
better.

As a user, I would sure like to see more information about the two major 
choices and a lot less "this is what was picked at an invitation-only 
meeting where one option wasn't represented"

David Lang
--
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