From: Chris Mason <chris.mason@oracle.com>
To: Aaron Straus <aaron@merfinllc.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] start work on delete snapshot code
Date: Mon, 09 Feb 2009 20:09:08 -0500 [thread overview]
Message-ID: <1234228148.17365.34.camel@think.oraclecorp.com> (raw)
In-Reply-To: <1234224453-4227-1-git-send-email-aaron@merfinllc.com>
On Mon, 2009-02-09 at 16:07 -0800, Aaron Straus wrote:
> This is far from complete and in particular it *doesn't* take the necessary
> locks at all i.e. please don't use this yet outside of testing. This patch is
> more of a request for help with regards to the locking.
>
Sorry to say that I won't have time to read through this in the morning,
but this is a pretty hefty task for a first patch. Thanks for taking it
on and posting this work!
-chris
next prev parent reply other threads:[~2009-02-10 1:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-10 0:07 [PATCH] start work on delete snapshot code Aaron Straus
2009-02-10 1:09 ` Chris Mason [this message]
2009-02-10 1:42 ` Aaron Straus
2009-02-10 19:44 ` Michele Petrazzo
2009-02-10 19:57 ` Aaron Straus
2009-02-10 20:27 ` Aaron Straus
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=1234228148.17365.34.camel@think.oraclecorp.com \
--to=chris.mason@oracle.com \
--cc=aaron@merfinllc.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