From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Remove certain calls for releasing page cache
Date: Thu, 31 Jul 2014 05:53:51 +0000 (UTC) [thread overview]
Message-ID: <pan$2dd8b$8ee08dd2$83d9cc3a$b36b9501@cox.net> (raw)
In-Reply-To: CAPDOMVgM+E1XxsFvhAYWzHo7HCFqp6sO6Y53_m2am-fno6m_AQ@mail.gmail.com
Nick Krause posted on Thu, 31 Jul 2014 00:14:50 -0400 as excerpted:
> I am wondering if some one can
> give me a pointer on where to download the git repos for the btrfs user
> spaces tools as it seems on the btrfs tools on the wiki.
https://btrfs.wiki.kernel.org/index.php/Btrfs_source_repositories#btrfs-progs_git_repository
You mean the URLs listed there? The official repo listed there is the same one
found in the gentoo btrfs-progs live-ebuild, for those (like me) that prefer
that to the versioned ebuild. I've no reason to believe that the integration
-branch URLs listed there are invalid, either, tho I've personally stuck to the
offical repo, master branch, which as of the last time I did an update was still
at v3.14.2, tho I've seen enough patches on the list I'm expecting a v3.16
release shortly after the v3.16 kernel release.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
next prev parent reply other threads:[~2014-07-31 5:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-30 20:42 [PATCH] Remove certain calls for releasing page cache Nicholas Krause
2014-07-30 20:47 ` Josef Bacik
2014-07-30 20:51 ` Zach Brown
2014-07-30 22:34 ` Nick Krause
2014-07-30 23:18 ` Josef Bacik
2014-07-30 23:30 ` Dave Airlie
2014-07-31 2:05 ` Nick Krause
2014-07-31 3:57 ` Dave Airlie
2014-07-31 4:14 ` Nick Krause
2014-07-31 5:53 ` Duncan [this message]
2014-07-31 10:11 ` Hugo Mills
2014-07-31 16:48 ` Nick Krause
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='pan$2dd8b$8ee08dd2$83d9cc3a$b36b9501@cox.net' \
--to=1i5t5.duncan@cox.net \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@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 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.