From: "Jose R. Santos" <jrs@us.ibm.com>
To: Theodore Tso <tytso@mit.edu>
Cc: Valerie Clement <valerie.clement@bull.net>, linux-ext4@vger.kernel.org
Subject: Re: E2fsprogs git tree
Date: Tue, 7 Aug 2007 12:39:56 -0500 [thread overview]
Message-ID: <20070807123956.45a36bfa@rx8> (raw)
In-Reply-To: <20070807172814.GA21522@thunk.org>
On Tue, 7 Aug 2007 13:28:14 -0400
Theodore Tso <tytso@mit.edu> wrote:
> On Tue, Aug 07, 2007 at 06:23:46PM +0200, Valerie Clement wrote:
> > Hi Ted,
> >
> > I tried to clone the source tree but it failed.
> >
> > The command "git-clone
> > http://www.kernel.org/pub/scm/fs/ext2/e2fsprogs.git" failed with :
> > "error: Could not interpret tags/APPLE_UUID_SNAP_1 as something to
> > pull"
> >
> > The command "git-clone http://repo.or.cz/r/e2fsprogs.git" failed
> > with: "error: Can't lock ref"
>
> What version of git are you using? Make sure you are using something
> which is at least git 1.5.x.
I get the same error as Valerie when using version 1.4.4.2. The same
version worked a couple of weeks ago when using the http URL.
>
> BTW, the better URL's to use are:
>
> git clone git://git.kernel.org/pub/scm/fs/ext2/e2fsprogs.git
>
> or
>
> git clone git://repo.or.cz/e2fsprogs.git
This seems to works fine using my older version of git.
> The http walkers are *much* more inefficient. I did try out git-clone
> using the http URL's, and it works, but it's slow. The other
> possibility is that you have some kind of nasty http transparent proxy
> which is corrupting the http protocol stream. This is why the git
> transport is seriously the much, much, MUCH better alternative.
>
>
> - Ted
-JRS
next prev parent reply other threads:[~2007-08-07 17:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-09 15:02 E2fsprogs git tree Theodore Ts'o
2007-08-07 16:23 ` Valerie Clement
2007-08-07 16:52 ` Coly Li
2007-08-07 17:28 ` Theodore Tso
2007-08-07 17:39 ` Jose R. Santos [this message]
2007-08-08 14:29 ` Theodore Tso
2007-08-08 8:31 ` Valerie Clement
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=20070807123956.45a36bfa@rx8 \
--to=jrs@us.ibm.com \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
--cc=valerie.clement@bull.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;
as well as URLs for NNTP newsgroup(s).