From: Marc MERLIN <marc@merlins.org>
To: Eric Wheeler <bcache@lists.ewheeler.net>
Cc: Kent Overstreet <kent.overstreet@gmail.com>,
linux-bcache@vger.kernel.org
Subject: Re: Hard to delete/unregister caching device
Date: Wed, 24 Feb 2016 13:30:05 -0800 [thread overview]
Message-ID: <20160224213005.GA19938@merlins.org> (raw)
In-Reply-To: <alpine.LRH.2.11.1602241911490.32077@mail.ewheeler.net>
On Wed, Feb 24, 2016 at 07:13:18PM +0000, Eric Wheeler wrote:
> It is, or at least it would be ideal to have up to date. By all means,
> write a patch and submit it! Documentation patches are some of the most
> important to support the userbase.
Sounds good, I'll look into that then.
Marc
--
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
Microsoft is to operating systems ....
.... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/
next prev parent reply other threads:[~2016-02-24 21:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-24 19:13 Hard to delete/unregister caching device Eric Wheeler
2016-02-24 21:30 ` Marc MERLIN [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-02-19 6:48 Marc MERLIN
2016-02-21 4:17 ` Kent Overstreet
2016-02-21 21:22 ` Marc MERLIN
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=20160224213005.GA19938@merlins.org \
--to=marc@merlins.org \
--cc=bcache@lists.ewheeler.net \
--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