public inbox for linux-bcache@vger.kernel.org
 help / color / mirror / Atom feed
From: Ming Lin <mlin@kernel.org>
To: Kent Overstreet <kent.overstreet@gmail.com>
Cc: "linux-bcache@vger.kernel.org" <linux-bcache@vger.kernel.org>
Subject: Re: [ANNOUNCE] bcachefs!
Date: Fri, 17 Jul 2015 22:21:03 -0700	[thread overview]
Message-ID: <1437196863.4737.2.camel@hasee> (raw)
In-Reply-To: <20150718021007.GA3196@kmo-pixel>

On Fri, 2015-07-17 at 19:10 -0700, Kent Overstreet wrote:
> BTW - probably the most valuable thing you could help out with is the
> documentation, in particular the guide:
> http://bcache.evilpiepirate.org/BcacheGuide/
> 
> Can you read through (at least some of) that, and tell me what's useful and what
> needs clarifying? And tell me what you'd like to see added to the guide next -
> I'll try and work on documentation over the next two weeks, since I probably
> won't be able to do much real coding with my test machines offline.

Yes, I'll read through that.

  reply	other threads:[~2015-07-18  5:21 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-14  0:58 [ANNOUNCE] bcachefs! Kent Overstreet
     [not found] ` <CACaajQtwx45r8GcRmchrQwDts1GH-V8g0x1FwGfDvnfm02bq+Q@mail.gmail.com>
2015-07-14  8:11   ` Kent Overstreet
2015-07-20  1:11     ` Denis Bychkov
     [not found]       ` <CAC7rs0uWSt85F443PRw1zvybccg+EfebaSyH9EhUwHjhTGryRA@mail.gmail.com>
     [not found]         ` <CAC7rs0upqkuH1CPd-OAmrpQ=8PmaDpzHYY1MaBDpAL6TS_iKyw@mail.gmail.com>
2015-07-20  2:52           ` Denis Bychkov
2015-07-24 19:25             ` Kent Overstreet
2015-07-15  6:11 ` Ming Lin
     [not found]   ` <CAC7rs0sbg2ci6=niQ0X11AONZbr2AOYhRbxfDH_w4N4A7dyPLw@mail.gmail.com>
2015-07-15  7:15     ` Ming Lin
2015-07-15  7:39       ` Ming Lin
2015-07-17 23:17         ` Kent Overstreet
2015-07-17 23:35           ` Ming Lin
2015-07-17 23:40             ` Kent Overstreet
2015-07-17 23:48               ` Ming Lin
2015-07-17 23:51                 ` Kent Overstreet
2015-07-17 23:58                   ` Ming Lin
2015-07-18  2:10                     ` Kent Overstreet
2015-07-18  5:21                       ` Ming Lin [this message]
2015-07-22  5:11                         ` Ming Lin
2015-07-22  5:15                           ` Ming Lin
2015-07-24 19:15                           ` Kent Overstreet
2015-07-24 20:47                             ` Ming Lin
2015-07-28 18:41                               ` Ming Lin
2015-07-28 18:45                                 ` Ming Lin
2015-08-06  6:40                                   ` Ming Lin
2015-08-06 23:11                                     ` Kent Overstreet
2015-08-07  5:21                                       ` Ming Lin
2015-08-06 22:58                                 ` Kent Overstreet
2015-08-06 23:27                                   ` Ming Lin
2015-08-06 23:59                                     ` Kent Overstreet
2015-07-18  0:01 ` Denis Bychkov
2015-07-18  2:12   ` Kent Overstreet
2015-07-19  7:46     ` Denis Bychkov
2015-07-21 18:37 ` David Mohr
2015-07-21 21:53   ` Jason Warr
2015-07-24 19:32     ` Kent Overstreet
2015-07-24 19:42       ` Jason Warr
2015-07-22  7:19   ` Killian De Volder

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=1437196863.4737.2.camel@hasee \
    --to=mlin@kernel.org \
    --cc=kent.overstreet@gmail.com \
    --cc=linux-bcache@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