linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Coly Li <coyli@suse.de>
To: linux-ext4@vger.kernel.org
Cc: Theodore Ts'o <tytso@mit.edu>, linux-ext4@vger.kernel.org
Subject: Re: E2fsprogs git tree
Date: Wed, 08 Aug 2007 00:52:05 +0800	[thread overview]
Message-ID: <46B8A335.3070400@suse.de> (raw)
In-Reply-To: <46B89C92.5060302@bull.net>

Valerie,

How about this:

git clone git://git.kernel.org/pub/scm/fs/ext2/e2fsprogs.git

It works for me.

Valerie Clement wrote:
> Theodore Ts'o wrote:
>> People may have noticed that e2fsprogs 1.40 and roughly a week later
>> e2fsprogs 1.40.1 have been released, while there hasn't been any
>> activity at http://thunk.org/hg/e2fsprogs.  That's because right after
>> e2fsprogs 1.40, I have moved the e2fsprogs development activity over to
>> git.  The public repositories can be found here:
>>
>>     http://www.kernel.org/pub/scm/fs/ext2/e2fsprogs.git
>>     git://git.kernel.org/pub/scm/fs/ext2/e2fsprogs.git
>>
>> and here:
>>
>>     git://repo.or.cz/e2fsprogs.git
>>     http://repo.or.cz/r/e2fsprogs.git
>>
> 
> 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"
> 
> Could you have a look at this please?
> Thank you very much,
>    Val�rie
> 

  reply	other threads:[~2007-08-07 16:51 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 [this message]
2007-08-07 17:28   ` Theodore Tso
2007-08-07 17:39     ` Jose R. Santos
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=46B8A335.3070400@suse.de \
    --to=coyli@suse.de \
    --cc=linux-ext4@vger.kernel.org \
    --cc=tytso@mit.edu \
    /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).