From: Chris Mason <chris.mason@oracle.com>
To: devzero@web.de
Cc: linux-btrfs@vger.kernel.org
Subject: Btrfs standalone tree regenerated
Date: Mon, 15 Dec 2008 15:55:51 -0500 [thread overview]
Message-ID: <1229374551.16295.26.camel@think.oraclecorp.com> (raw)
In-Reply-To: <541783609@web.de>
On Sun, 2008-12-14 at 00:16 +0100, devzero@web.de wrote:
> Hello !
>
> is there a way to get btrfs-unstable source without using git ?
>
> i`m trying for a while now, but it seems git doesn`t work as desired on my system or the problem is that i`m behind http proxy.
>
> what about some unstable snapshots in http://www.kernel.org/pub/linux/kernel/people/mason/btrfs/ ?
Hello everyone,
I've redone the standalone tree because it had a broken commit in it.
If you're pulling from the standalone tree, you might need to clone it
from scratch to avoid having a repo with two heads.
Sorry for the hassle, I didn't realize the initial setup of the stand
alone tree wasn't quite right.
The good news is that http pulls should work now.
-chris
prev parent reply other threads:[~2008-12-15 20:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-13 23:16 daily snapshots ? devzero
2008-12-15 20:55 ` Chris Mason [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=1229374551.16295.26.camel@think.oraclecorp.com \
--to=chris.mason@oracle.com \
--cc=devzero@web.de \
--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