From: Theodore Tso <tytso@mit.edu>
To: "Jose R. Santos" <jrs@us.ibm.com>
Cc: Valerie Clement <valerie.clement@bull.net>, linux-ext4@vger.kernel.org
Subject: Re: E2fsprogs git tree
Date: Wed, 8 Aug 2007 10:29:06 -0400 [thread overview]
Message-ID: <20070808142906.GB11847@thunk.org> (raw)
In-Reply-To: <20070807123956.45a36bfa@rx8>
On Tue, Aug 07, 2007 at 12:39:56PM -0500, Jose R. Santos wrote:
> 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.
I'd strongly advise that you use git 1.5.x and update to use a 1.5
style clone of the repository. It's much, MUCH, easier to use than
git 1.4....
- Ted
next prev parent reply other threads:[~2007-08-08 14:29 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
2007-08-08 14:29 ` Theodore Tso [this message]
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=20070808142906.GB11847@thunk.org \
--to=tytso@mit.edu \
--cc=jrs@us.ibm.com \
--cc=linux-ext4@vger.kernel.org \
--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).