From: Jeff King <peff@peff.net>
To: Brian Gernhardt <benji@silverinsanity.com>
Cc: Git List <git@vger.kernel.org>
Subject: Re: git remote rm non-existant-remote
Date: Mon, 29 Jun 2009 12:38:43 -0400 [thread overview]
Message-ID: <20090629163842.GA12855@sigio.peff.net> (raw)
In-Reply-To: <C1DD7597-AAFF-4F79-B11C-4D6BE9EB2601@silverinsanity.com>
On Sun, Jun 28, 2009 at 07:04:17PM -0400, Brian Gernhardt wrote:
> >Ouch. That is indeed a serious bug. However, I can't reproduce with
> >current 'next'; which version of git are you using?
>
> git version 1.6.3.3.467.g98a79
>
> I believe that's the latest "next".
OK, then it is not a version problem, but rather I am doing something
different to try to reproduce it. Can you post a short set of commands
to show the problem?
-Peff
prev parent reply other threads:[~2009-06-29 16:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-28 14:47 git remote rm non-existant-remote Brian Gernhardt
2009-06-28 16:11 ` Jeff King
2009-06-28 23:04 ` Brian Gernhardt
2009-06-29 16:38 ` Jeff King [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=20090629163842.GA12855@sigio.peff.net \
--to=peff@peff.net \
--cc=benji@silverinsanity.com \
--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).