public inbox for linux-nfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Benny Halevy <bhalevy@panasas.com>
To: Andy Adamson <andros@netapp.com>
Cc: "J. Bruce Fields" <bfields@fieldses.org>,
	Dean Hildebrand <seattleplus@gmail.com>,
	"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: Re: Linux pNFS status meeting  6/10/10
Date: Thu, 10 Jun 2010 17:46:19 +0300	[thread overview]
Message-ID: <4C10FABB.7020506@panasas.com> (raw)
In-Reply-To: <5967A1F5-CE19-46A3-A6EC-4EA84FBD5034@netapp.com>

On Jun. 10, 2010, 17:39 +0300, Andy Adamson <andros@netapp.com> wrote:
> NetApp has an internal meeting that lasts until 1:00 EST. I know it's  
> late - but could we start a 1/2 hour later?
> 

OK with me.

> -->Andy
> 
> On Jun 10, 2010, at 10:35 AM, J. Bruce Fields wrote:
> 
>> On Wed, Jun 09, 2010 at 11:20:58AM -0700, Dean Hildebrand wrote:
>>> Meeting on Thursday 6/10/2010 at 9:30 AM PDT (12:30 PM EST).
>>
>> Rough agenda:
>>
>> 1. upstream status/merge plans (trond, bfields)
>>
>> 2. State of pNFS tree (bhalevy)
>>
>> 3. Client
>> 	3.1. Client pNFS status
>> 	3.2. Client state management design documentation (trond)
>> 	3.3. Block device discovery design
>>
>> 4. Server
>> 	4.1. Todo's for minimal 4.1 server (bfields)
>> 	4.2. pnfs
>> 		pnfs/gfs2
>> 		exofs
>>
>> 5. redhat status (steved)
>>
>> 6. bakeathon plans
>> 	- ann arbor:
>> 	- boston
>>
>> 7. new business
>>
>> 8. next meeting
>>
>> --b.
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-nfs"  
>> in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2010-06-10 14:46 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-09 18:20 Linux pNFS status meeting 6/10/10 Dean Hildebrand
2010-06-10 14:35 ` J. Bruce Fields
2010-06-10 14:39   ` Andy Adamson
2010-06-10 14:44     ` J. Bruce Fields
2010-06-10 17:11       ` sfaibish
     [not found]         ` <op.vd3gpvp0unckof-sXut7+96orlxdPWQvOaHCoI83tS8F2Zb0E9HWUfgJXw@public.gmane.org>
2010-06-10 17:12           ` William A. (Andy) Adamson
2010-06-10 14:46     ` Benny Halevy [this message]
2010-06-10 16:38       ` Dean Hildebrand
2010-06-10 17:07         ` William A. (Andy) Adamson
     [not found]           ` <AANLkTilHI_pte9auBl3Z1dcnkDY_Vdne8WVAX8QlGnVa-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-06-10 17:09             ` Benny Halevy
2010-06-10 17:14               ` Staubach_Peter
     [not found]                 ` <BF3BB6D12298F54B89C8DCC1E4073D8001419B24-1Zg0zMUlrbd9m/dOYFj4Yjjd7nCn89gW@public.gmane.org>
2010-06-10 17:16                   ` Benny Halevy
2010-06-10 17:16                     ` William A. (Andy) Adamson
2010-06-10 17:17                     ` Staubach_Peter
     [not found]                       ` <BF3BB6D12298F54B89C8DCC1E4073D8001419B32-1Zg0zMUlrbd9m/dOYFj4Yjjd7nCn89gW@public.gmane.org>
2010-06-10 17:19                         ` William A. (Andy) Adamson
2010-06-10 17:38 ` J. Bruce Fields

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=4C10FABB.7020506@panasas.com \
    --to=bhalevy@panasas.com \
    --cc=andros@netapp.com \
    --cc=bfields@fieldses.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=seattleplus@gmail.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