public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Vladislav Bolkhovitin <vst@vlnb.net>
To: Arjan van de Ven <arjan@infradead.org>
Cc: James Bottomley <James.Bottomley@HansenPartnership.com>,
	"Nicholas A. Bellinger" <nab@linux-iscsi.org>,
	linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: Spamming linux-kernel and linux-scsi by out-of-tree patches (LIO)
Date: Mon, 26 Jan 2009 19:44:48 +0300	[thread overview]
Message-ID: <497DE880.1060301@vlnb.net> (raw)
In-Reply-To: <20090126081905.7c112170@infradead.org>

Arjan van de Ven, on 01/26/2009 07:19 PM wrote:
> On Mon, 26 Jan 2009 19:08:24 +0300
> Vladislav Bolkhovitin <vst@vlnb.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

  reply	other threads:[~2009-01-26 16:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-26 13:17 Spamming linux-kernel and linux-scsi by out-of-tree patches (LIO) Vladislav Bolkhovitin
2009-01-26 15:37 ` James Bottomley
2009-01-26 16:08   ` Vladislav Bolkhovitin
2009-01-26 16:19     ` Arjan van de Ven
2009-01-26 16:44       ` Vladislav Bolkhovitin [this message]
2009-01-26 17:15       ` Nicholas A. Bellinger
2009-01-26 16:37     ` James Bottomley

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=497DE880.1060301@vlnb.net \
    --to=vst@vlnb.net \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=arjan@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=nab@linux-iscsi.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox