All of lore.kernel.org
 help / color / mirror / Atom feed
From: Morey Roof <moreyroof@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: Btrfs conf call
Date: Wed, 13 Aug 2008 11:46:18 -0600	[thread overview]
Message-ID: <48A31DEA.5090903@gmail.com> (raw)
In-Reply-To: <1218645196.15342.363.camel@think.oraclecorp.com>

Could someone write a quick recap of this for those of us who are 
interested and happened to miss it?

Thanks,

Morey

Chris Mason wrote:
> Hello everyone,
>
> This notice went out last night as well, but the mail servers seem to
> have lost it.  So, sorry for the late notice, but our regular bi-weekly
> btrfs conf call will be today (Wednesday):
>
> Time: 1:30pm US Eastern (10:30am Pacific)
>
> * Dial-in Number(s):
> * Toll: 1-314-655-1416
> * Toll Free: 1-877-422-0049
> *
> * Participant Pin access code: 209652
>
> The agenda will cover issues found in v0.16 and patches in progress for
> the next release.
>
> -chris
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>   


  reply	other threads:[~2008-08-13 17:46 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-13 16:33 Btrfs conf call Chris Mason
2008-08-13 17:46 ` Morey Roof [this message]
2008-08-13 20:22   ` jim owens
2008-08-13 21:02     ` Morey Roof
2008-08-13 21:30       ` jim owens
  -- strict thread matches above, loose matches on Subject: below --
2008-08-27 13:21 Chris Mason
2008-08-28 13:14 ` Miguel Sousa Filipe
2008-08-28 17:44   ` jim owens
2008-09-10 15:29 Chris Mason
2008-09-16 19:05 ` jj
2008-09-16 19:31   ` Jeff Schroeder
2008-09-16 20:03     ` Eric Anopolsky
2008-11-05  1:20 Btrfs Conf call Chris Mason
2008-11-19  1:03 Chris Mason
2009-02-18  1:20 Btrfs Conf Call Chris Mason
2009-03-04 13:59 Btrfs conf call Chris Mason
2009-03-18 14:23 Chris Mason
2009-04-01 13:14 Btrfs Conf Call Chris Mason
2009-04-15 13:08 Btrfs Conf call Chris Mason

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=48A31DEA.5090903@gmail.com \
    --to=moreyroof@gmail.com \
    --cc=linux-btrfs@vger.kernel.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.