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: <497DE880.1060301@vlnb.net>
Date:	Mon, 26 Jan 2009 19:44:48 +0300
From:	Vladislav Bolkhovitin <vst@...b.net>
To:	Arjan van de Ven <arjan@...radead.org>
CC:	James Bottomley <James.Bottomley@...senPartnership.com>,
	"Nicholas A. Bellinger" <nab@...ux-iscsi.org>,
	linux-kernel@...r.kernel.org, linux-scsi@...r.kernel.org
Subject: Re: Spamming linux-kernel and linux-scsi by out-of-tree patches (LIO)

Arjan van de Ven, on 01/26/2009 07:19 PM wrote:
> On Mon, 26 Jan 2009 19:08:24 +0300
> Vladislav Bolkhovitin <vst@...b.net> wrote:
> 
>> I wouldn't object if Nicholas des the same and send in linux-scsi
>> and linux-kernel a complete patchset, which we will review and
>> discuss. But he sends *intermediate* patches and this looks for me
>> like a violation of fundamental rules/intention of Linux kernel
>> mailing lists, hence I complain.
>>
>> So, should I understand your words that you agree if I also start 
>> sending intermediate patches for SCST to linux-scsi/linux-kernel?
>>
> 
> 
> <looking in as an outsider>
> 
> I am thoroughly surprised by this email exchange.
> From where I sit, there is almost no such thing as posting patches too
> early. Really. Transparency and early review/feedaback is by far
> more important than ignoring a few more patches in an area you
> don't careabout.

Sure. All projects (including LIO) have own mailing list(s) for such 
review/feedback, but at the moment LIO and Linux kernel are completely 
separated projects.

Anyway, I could just misunderstand the intention and policy of Linux 
kernel mailing lists. I apologize, if so.

> Your second paragraph makes me wonder if your email is more political
> than technical in nature. But either way, you should feel encouraged
> to release early, release often.

There's not much politic in it. Simply what Nicholas Bellinger does 
violated my understanding of what allowed in Linux kernel mailing lists, 
so I wondered, if what allowed for Nicholas Bellinger allowed for me as 
well.

Vlad
--
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