git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Martin Langhoff" <martin.langhoff@gmail.com>
To: "Martin Langhoff" <martin.langhoff@gmail.com>,
	"Git Mailing List" <git@vger.kernel.org>,
	"Keith Packard" <keithp@keithp.com>
Subject: Re: parsecvs repository moved...
Date: Mon, 16 Apr 2007 20:37:09 +1200	[thread overview]
Message-ID: <46a038f90704160137j3c6ffe5es3e44a6342017db58@mail.gmail.com> (raw)
In-Reply-To: <20070416075829.GK2689@curie-int.orbis-terrarum.net>

On 4/16/07, Robin H. Johnson <robbat2@gentoo.org> wrote:
> On Mon, Apr 16, 2007 at 07:32:58PM +1200, Martin Langhoff wrote:
> >  I've just found that parsecvs.git repo has moved again... to
> >  http://anongit.freedesktop.org/git/users/keithp/repos/parsecvs.git
> It seems to be broken on there?
>
> $ git clone http://anongit.freedesktop.org/git/users/keithp/repos/parsecvs.git
> Initialized empty Git repository in /code/vcs/parsecvs/.git/
> Cannot get remote repository information.
> Perhaps git-update-server-info needs to be run there?

Oh - I managed to run an update to an existing checkout of mine - but
it's broken for cloning over http. I'm happy to publish my cloned repo
- try

 git-clone http://git.catalyst.net.nz/parsecvs.git

cheers,


martin

  reply	other threads:[~2007-04-16  8:37 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-16  7:32 parsecvs repository moved Martin Langhoff
2007-04-16  7:58 ` Robin H. Johnson
2007-04-16  8:37   ` Martin Langhoff [this message]
2007-04-16  8:44     ` Robin H. Johnson
2007-04-16  8:39   ` Martin Langhoff
2007-04-16  8:42     ` Robin H. Johnson
2007-04-16  8:51       ` Martin Langhoff
2007-04-16  8:55         ` Martin Langhoff
2007-04-16 11:48         ` Robin H. Johnson
2007-04-16  8:45     ` Junio C Hamano
2007-04-16  8:59       ` Martin Langhoff
2007-04-16 11:21 ` James Cloos
2007-04-27 15:15   ` Petr Baudis

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=46a038f90704160137j3c6ffe5es3e44a6342017db58@mail.gmail.com \
    --to=martin.langhoff@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=keithp@keithp.com \
    /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).