From: Daniel Cordero <theappleman@gmail.com>
To: Roy Sigurd Karlsbakk <roy@karlsbakk.net>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: New experimental btrfs branch ready for testing
Date: Sun, 7 Jun 2009 13:13:41 +0100 [thread overview]
Message-ID: <20090607121341.GA11706@cumin.applehq.eu> (raw)
In-Reply-To: <8B019CAA-9B37-4403-B5FB-A925A17C045A@karlsbakk.net>
On Sun, Jun 07, 2009 at 01:50:27PM +0200, Roy Sigurd Karlsbakk wrote:
> On 1. juni. 2009, at 23.04, Chris Mason wrote:
>
>> I've setup git branches called newformat where you can pull the new
>> code.
>>
>> For the kernel (based on 2.6.30-rc7):
>>
>> git pull git://git.kernel.org/pub/scm/linux/kernel/git/mason/btrfs-
>> unstable.git newformat
>
> # git pull git://git.kernel.org/pub/scm/linux/kernel/git/mason/btrfs-
> unstable.git newformat
> fatal: Not a git repository
>
>> For the progs:
>>
>> git pull git://git.kernel.org/pub/scm/linux/kernel/git/mason/btrfs-
>> progs-unstable.git newformat
>
> # git pull git://git.kernel.org/pub/scm/linux/kernel/git/mason/btrfs-
> progs-unstable.git newformat
> fatal: Not a git repository
>
>>
> Have this code been removed, or is it me doing something funny?
You're doing something funny.
I'm guessing you don't already have a copy of the btrfs repositories, so
you should be using clone instead of pull.
If you do have them, cd into them.
next prev parent reply other threads:[~2009-06-07 12:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-01 21:04 New experimental btrfs branch ready for testing Chris Mason
2009-06-02 13:28 ` Chris Mason
2009-06-03 17:08 ` Chris Mason
2009-06-04 19:02 ` Steven Pratt
2009-06-04 19:05 ` Chris Mason
2009-06-05 14:20 ` Chris Mason
2009-06-05 16:02 ` Steven Pratt
2009-06-05 21:27 ` Steven Pratt
2009-06-06 0:20 ` Chris Mason
2009-06-06 16:38 ` Steven Pratt
2009-06-09 15:26 ` Chris Mason
2009-06-15 15:46 ` Steven Pratt
2009-06-07 11:50 ` Roy Sigurd Karlsbakk
2009-06-07 12:13 ` Daniel Cordero [this message]
2009-06-08 12:33 ` Yan Zheng
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=20090607121341.GA11706@cumin.applehq.eu \
--to=theappleman@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=roy@karlsbakk.net \
/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