linux-bcache.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alex Pyrgiotis <apyrgio-Hpc4xzY4zrDSDkk6z29a7FAUjnlXr6A1@public.gmane.org>
To: linux-bcache-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Userspace tools and git repo
Date: Fri, 11 May 2012 14:01:51 +0300	[thread overview]
Message-ID: <1336734111.3576.34.camel@dimension7> (raw)

Hi Kent,

I 've been following this project for quite a while (congrats for the
v13 of bcache) and I'm glad that the wiki has been revamped with more
details and current status. 
Today, I've been skimming through some of the stuff written there and I
saw this:

-------------------------------------
make-bcache -B -S <set-uuid> backing_device
The -B option to bcache indicates that a backing device is being created
The -S option allows the UUID of the cache set to be indicated so that
the attach process can be bypasses
<b>backing_device</b> is the path to the block device or partition that
will be used as a backing device
---------------------------------------

As far as I can tell, the -S option is not implemented in the userspace
tools.

Am I missing something? I've downloaded the sources for bcache-tools and
linux-bache from this git repo: 

git://evilpiepirate.org/~kent/
 
Is this repo up-to-date with your project?
 
I'm mainly asking since I can see that the latest changes were done
about a month ago and the site was updated 2-3 days ago.

Thanks,
Alex
-- 

Alex Pyrgiotis, a.k.a 03107422
Undergrad Student

School of Electrical & Computer Engineering
National Technical University of Athens, Greece

Paper Street Soap Co.
work: (288) 555-0153

             reply	other threads:[~2012-05-11 11:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-11 11:01 Alex Pyrgiotis [this message]
2012-05-11 20:35 ` Userspace tools and git repo Kent Overstreet

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=1336734111.3576.34.camel@dimension7 \
    --to=apyrgio-hpc4xzy4zrdsdkk6z29a7faujnlxr6a1@public.gmane.org \
    --cc=linux-bcache-u79uwXL29TY76Z2rM5mHXA@public.gmane.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;
as well as URLs for NNTP newsgroup(s).