From: Hugo Mills <hugo@carfax.org.uk>
To: David Brown <btrfs@davidb.org>
Cc: Chris Mason <chris.mason@oracle.com>,
Calvin Walton <calvin.walton@kepstin.ca>,
"debit2005@gmail.com" <debit2005@gmail.com>,
linux-btrfs@vger.kernel.org
Subject: Re: btrfsprogs source code
Date: Wed, 4 Jan 2012 18:37:45 +0000 [thread overview]
Message-ID: <20120104183745.GD27122@carfax.org.uk> (raw)
In-Reply-To: <20120104182419.GA11205@davidb.org>
[-- Attachment #1: Type: text/plain, Size: 1062 bytes --]
On Wed, Jan 04, 2012 at 10:24:20AM -0800, David Brown wrote:
> On Tue, Jan 03, 2012 at 01:05:07PM -0500, Calvin Walton wrote:
>
> >The best way to get the btrfs-progs source is probably via git; Chris
> >Mason's repository for it can be found at
> >http://git.kernel.org/?p=linux/kernel/git/mason/btrfs-progs.git
>
> Chris,
>
> The wiki at
> https://btrfs.wiki.kernel.org/articles/b/t/r/Btrfs_source_repositories.html
> still refers to a btrfs-progs-unstable.git repository, which is not
> present at git.kernel.org. Should we update this wiki, or do you have
> plans on pushing an unstable repository again?
That wiki is read-only, unfortunately. The up-to-date wiki is at
[1], and we'll be decanting that back onto the kernel.org one when the
kernel.org wiki is back in full working order.
Hugo.
[1] http://btrfs.ipv5.de/
--
=== Hugo Mills: hugo@... carfax.org.uk | darksatanic.net | lug.org.uk ===
PGP key: 515C238D from wwwkeys.eu.pgp.net or http://www.carfax.org.uk
--- echo "killall cat" > ~/curiosity.sh ---
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 190 bytes --]
prev parent reply other threads:[~2012-01-04 18:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-03 17:56 btrfsprogs source code debit2005
2012-01-03 18:05 ` Calvin Walton
2012-01-04 18:24 ` David Brown
2012-01-04 18:37 ` Hugo Mills [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=20120104183745.GD27122@carfax.org.uk \
--to=hugo@carfax.org.uk \
--cc=btrfs@davidb.org \
--cc=calvin.walton@kepstin.ca \
--cc=chris.mason@oracle.com \
--cc=debit2005@gmail.com \
--cc=linux-btrfs@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;
as well as URLs for NNTP newsgroup(s).