From: Eric Anopolsky <erpo41@gmail.com>
To: jeffschroeder@computer.org
Cc: jj <jj@mailinator.com>, linux-btrfs@vger.kernel.org
Subject: Re: Btrfs conf call
Date: Tue, 16 Sep 2008 14:03:31 -0600 [thread overview]
Message-ID: <1221595411.7738.0.camel@telesto> (raw)
In-Reply-To: <c24352ca0809161231j1c68bd3dk16b8f86cfa05c661@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 758 bytes --]
On Tue, 2008-09-16 at 12:31 -0700, Jeff Schroeder wrote:
> On Tue, Sep 16, 2008 at 12:05 PM, jj <jj@mailinator.com> wrote:
> > Chris Mason <chris.mason <at> oracle.com> writes:
> >
> >> Hello everyone,
> >>
> >> Our regular bi-weekly btrfs conf call will be today (Wednesday):
> > ...
> >> The agenda will cover status updates on the synchronous operations code,
> >> Yan's new backref work and Josef's allocator changes.
> >
> > Just wondering if anyone has a re-cap of the meeting?
>
> Would a recording of the conference call posted on the website be
> unreasonable to ask for? If people want to know these sorts of things
> but can't make the call perhaps it would save everyone time.
>
I would really like that.
Cheers,
Eric
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2008-09-16 20:03 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-10 15:29 Btrfs conf call Chris Mason
2008-09-16 19:05 ` jj
2008-09-16 19:31 ` Jeff Schroeder
2008-09-16 20:03 ` Eric Anopolsky [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-04-15 13:08 Btrfs Conf call Chris Mason
2009-04-01 13:14 Btrfs Conf Call Chris Mason
2009-03-18 14:23 Btrfs conf call Chris Mason
2009-03-04 13:59 Chris Mason
2009-02-18 1:20 Btrfs Conf Call Chris Mason
2008-11-19 1:03 Btrfs Conf call Chris Mason
2008-11-05 1:20 Chris Mason
2008-08-27 13:21 Btrfs conf call Chris Mason
2008-08-28 13:14 ` Miguel Sousa Filipe
2008-08-28 17:44 ` jim owens
2008-08-13 16:33 Chris Mason
2008-08-13 17:46 ` Morey Roof
2008-08-13 20:22 ` jim owens
2008-08-13 21:02 ` Morey Roof
2008-08-13 21:30 ` jim owens
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=1221595411.7738.0.camel@telesto \
--to=erpo41@gmail.com \
--cc=jeffschroeder@computer.org \
--cc=jj@mailinator.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox