All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <jaxboe@fusionio.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	philipp.reisner@linbit.com
Subject: Re: [GIT PULL] block/IO bits for 2.6.35-rc1
Date: Sun, 06 Jun 2010 13:23:06 +0200	[thread overview]
Message-ID: <4C0B851A.7050008@fusionio.com> (raw)
In-Reply-To: <alpine.LFD.2.00.1006041531340.8175@i5.linux-foundation.org>

On 2010-06-05 00:37, Linus Torvalds wrote:
> 
> 
> On Fri, 4 Jun 2010, Jens Axboe wrote:
>>
>> - A drbd update.
> 
> Can we agree to just stop this? 
> 
> During the merge window, please. The drbd fiasco has been going on too 
> long for me to believe in the whole "a few more fixes" thing.
> 
> If it's a security issue, or a major oops, take it. But don't send me 
> "updates" or stuff "just to make it work", since it never has before.
> 
> It's not a regression that drbd is in bad shape. So don't try to make it 
> out to be one. And if it's not a regression or a major oops/security 
> issue, it goes into the NEXT MERGE WINDOW.
> 
> Yes, I'm annoyed. Somebody needs to call out the drbd crud. I really don't 
> want _any_ more drbd crap after the merge window. If I see any more, I'll 
> stop pulling. Comprende?

Understood, I should have been a bit more strict on accepting
late drbd chages.

-- 
Jens Axboe


      reply	other threads:[~2010-06-06 11:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-04 12:53 [GIT PULL] block/IO bits for 2.6.35-rc1 Jens Axboe
2010-06-04 22:37 ` Linus Torvalds
2010-06-06 11:23   ` Jens Axboe [this message]

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=4C0B851A.7050008@fusionio.com \
    --to=jaxboe@fusionio.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=philipp.reisner@linbit.com \
    --cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.