From: Eric Sandeen <sandeen@redhat.com>
To: Nick Krause <xerofoify@gmail.com>,
Wang Shilong <wangshilong1991@gmail.com>
Cc: Martin Steigerwald <Martin@lichtvoll.de>,
Hugo Mills <hugo@carfax.org.uk>,
"linux-btrfs@vger.kernel.org SYSTEM list:BTRFS FILE"
<linux-btrfs@vger.kernel.org>
Subject: Re: Help with Project on brtfs wiki
Date: Sat, 26 Jul 2014 21:15:44 -0500 [thread overview]
Message-ID: <53D460D0.4050606@redhat.com> (raw)
In-Reply-To: <CAPDOMVh+46smsvw9r6XG++acU-EkKpgDh0wx=03XFjbYQYszPQ@mail.gmail.com>
On 7/26/14, 8:43 PM, Nick Krause wrote:
...
> Fine then I guess I need to read the documentation and other things on my own.
> Seems everyone here wants me to figure out everything on my own.
Hugo bent over backwards, twice, to give you very good advice. So did
Steven Rostedt on LKML. You should follow it, and see how things go
from there.
-Eric
> Nick
prev parent reply other threads:[~2014-07-27 2:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-25 23:16 Help with Project on brtfs wiki Nick Krause
2014-07-26 10:05 ` Hugo Mills
2014-07-26 10:32 ` Martin Steigerwald
2014-07-26 11:07 ` Wang Shilong
2014-07-27 1:43 ` Nick Krause
2014-07-27 2:05 ` Chris Murphy
2014-07-27 2:14 ` Nick Krause
2014-07-27 2:15 ` Eric Sandeen [this message]
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=53D460D0.4050606@redhat.com \
--to=sandeen@redhat.com \
--cc=Martin@lichtvoll.de \
--cc=hugo@carfax.org.uk \
--cc=linux-btrfs@vger.kernel.org \
--cc=wangshilong1991@gmail.com \
--cc=xerofoify@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 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.