linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Doug Ledford <dledford@redhat.com>
To: Neil Brown <neilb@suse.de>
Cc: Dan Williams <dan.j.williams@intel.com>,
	"Ciechanowski, Ed" <ed.ciechanowski@intel.com>,
	"Hawrylewicz Czarnowski,
	Przemyslaw" <przemyslaw.hawrylewicz.czarnowski@intel.com>,
	"Labun, Marcin" <Marcin.Labun@intel.com>,
	linux-raid <linux-raid@vger.kernel.org>
Subject: Re: [mdadm GIT PULL] rebuild checkpoints, incremental assembly, volume delete/rename, and fixes
Date: Wed, 07 Jul 2010 10:03:33 -0400	[thread overview]
Message-ID: <4C348935.5070303@redhat.com> (raw)
In-Reply-To: <20100707081701.4765f770@notabene.brown>

[-- Attachment #1: Type: text/plain, Size: 1312 bytes --]

On 07/06/2010 06:17 PM, Neil Brown wrote:
> On Tue, 06 Jul 2010 17:43:37 -0400
> Doug Ledford <dledford@redhat.com> wrote:
> 
>>> I'm fairly seriously considering cutting a 3.1.3 shortly (Thursday?) so that
>>> I have a clean slate to build the policy frame work and aim it for 3.2.0.
>>>
>>> If you have anything that you would like to see included in (or addressed
>>> for) 3.1.3, please let me know.
>>>
>>> Thanks,
>>> NeilBrown
>>
>> Hey Neil, I'm just back on the job.  I'd appreciate a few days to go
>> through all my bugs and see what items not related to the policy
>> framework might need fixed from my perspective for a 3.1.3 release.
>> Thanks ;-)
>>
> 
> Welcome back!
> If it isn't Thursday then it probably wont be for a couple of weeks as I am
> travelling next week (and recovering from jet-lag the week after).
> 
> Let's say July 22nd is the release date for 3.1.3.
> 
> NeilBrown

Well, I *might* have the pull request to you in time for a Thursday
release, so we can say as a conservative date the 22nd, but possibly the
8th if things go well.

-- 
Doug Ledford <dledford@redhat.com>
              GPG KeyID: CFBFF194
	      http://people.redhat.com/dledford

Infiniband specific RPMs available at
	      http://people.redhat.com/dledford/Infiniband


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2010-07-07 14:03 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-27  0:50 [mdadm GIT PULL] rebuild checkpoints, incremental assembly, volume delete/rename, and fixes Dan Williams
2010-05-31  1:37 ` Neil Brown
2010-06-11  6:42   ` Dan Williams
2010-06-16  6:33     ` Neil Brown
2010-07-02  0:56       ` Dan Williams
2010-07-06  4:50         ` Neil Brown
2010-07-06 19:51           ` fixes for 3.1.3 (was: Re: [mdadm GIT PULL] rebuild checkpoints...) Dan Williams
2010-07-21 18:04             ` Dan Williams
2010-07-22  7:47               ` Neil Brown
2010-07-06 21:43           ` [mdadm GIT PULL] rebuild checkpoints, incremental assembly, volume delete/rename, and fixes Doug Ledford
2010-07-06 22:17             ` Neil Brown
2010-07-07 14:03               ` Doug Ledford [this message]
2010-07-08  7:50                 ` Neil Brown

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=4C348935.5070303@redhat.com \
    --to=dledford@redhat.com \
    --cc=Marcin.Labun@intel.com \
    --cc=dan.j.williams@intel.com \
    --cc=ed.ciechanowski@intel.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=neilb@suse.de \
    --cc=przemyslaw.hawrylewicz.czarnowski@intel.com \
    /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;
as well as URLs for NNTP newsgroup(s).