From: "Shawn O. Pearce" <spearce@spearce.org>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Guido Ostkamp <git@ostkamp.fastmail.fm>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: [BUG] git remote add failure
Date: Thu, 18 Oct 2007 20:20:17 -0400 [thread overview]
Message-ID: <20071019002017.GP14735@spearce.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0710181708230.25221@racer.site>
Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:
> On Thu, 18 Oct 2007, Guido Ostkamp wrote:
>
> > 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.
>
> The problem there is of course that the fetch could fail because you are
> offline. In that case, you do not want git remote to throw the
> information away.
Right. But maybe there should be an easier way for the user to
"force" adding the remote over the existing remote. Much like how
they can force creating a branch over an existing branch.
Too bad -f is already taken. :-\
--
Shawn.
prev parent reply other threads:[~2007-10-19 0:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-18 8:55 [BUG] git remote add failure Guido Ostkamp
2007-10-18 16:09 ` Johannes Schindelin
2007-10-19 0:20 ` Shawn O. Pearce [this message]
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=20071019002017.GP14735@spearce.org \
--to=spearce@spearce.org \
--cc=Johannes.Schindelin@gmx.de \
--cc=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).