git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Guido Ostkamp" <git@ostkamp.fastmail.fm>
To: "Git Mailing List" <git@vger.kernel.org>
Subject: [BUG] git remote add failure
Date: Thu, 18 Oct 2007 10:55:19 +0200	[thread overview]
Message-ID: <1192697719.31199.1216526739@webmail.messagingengine.com> (raw)

Hello,

I think I've found a bug in "git remote add". I tried the following:

$ git remote add -f spearce2 http://repo.or.cz/git/spearce.git
Cannot get the repository state from http://repo.or.cz/git/spearce.git
fetch spearce2: command returned error: 1

Obviously I used the wrong URI. Then I tried again:

$ git remote add -f spearce2 http://repo.or.cz/r/git/spearce.git
remote spearce2 already exists.

I think Git should not store the bad info and block the name when the
first call wasn't successfull.

Regards

Guido

             reply	other threads:[~2007-10-18  8:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-18  8:55 Guido Ostkamp [this message]
2007-10-18 16:09 ` [BUG] git remote add failure Johannes Schindelin
2007-10-19  0:20   ` Shawn O. Pearce

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=1192697719.31199.1216526739@webmail.messagingengine.com \
    --to=git@ostkamp.fastmail.fm \
    --cc=git@vger.kernel.org \
    /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).