From: "J. Bruce Fields" Subject: Re: Linux pNFS status meeting 6/10/10 Date: Thu, 10 Jun 2010 10:44:13 -0400 Message-ID: <20100610144413.GG26427@fieldses.org> References: <4C0FDB8A.9010500@gmail.com> <20100610143506.GF26427@fieldses.org> <5967A1F5-CE19-46A3-A6EC-4EA84FBD5034@netapp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Dean Hildebrand , "linux-nfs@vger.kernel.org" To: Andy Adamson Return-path: Received: from fieldses.org ([174.143.236.118]:54416 "EHLO fieldses.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1759252Ab0FJOoQ (ORCPT ); Thu, 10 Jun 2010 10:44:16 -0400 In-Reply-To: <5967A1F5-CE19-46A3-A6EC-4EA84FBD5034@netapp.com> Sender: linux-nfs-owner@vger.kernel.org List-ID: On Thu, Jun 10, 2010 at 10:39:10AM -0400, Andy Adamson 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? It works for me, as long as we agree to keep the meeting short (I'd still like to be done by 1:30). Since most of us will be together next week to discuss the techincal stuff, maybe we should just keep it to: - pre-bakeathon questions - meeting scheduling for next week. (We talked about reserving a room for pnfs client issues, at least.) --b. > > -->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 >