From: Tim Visher <tim.visher@gmail.com>
To: Ramkumar Ramachandra <artagnon@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: Getting rid of a stale remote?
Date: Tue, 6 Apr 2010 14:25:07 -0400 [thread overview]
Message-ID: <x2uc115fd3c1004061125i695f66bbi9f949ccc1958750@mail.gmail.com> (raw)
In-Reply-To: <w2if3271551004061107rb25b83b9p19a284f19e7d4f87@mail.gmail.com>
On Tue, Apr 6, 2010 at 2:07 PM, Ramkumar Ramachandra <artagnon@gmail.com> wrote:
>> I'm trying to get rid of a stale remote. I deleted the remote via
>> `git remote rm <remote>` and that removed it from .git/config but for
>> some reason the references stayed in the listing of `git branch -a`.
>
> See `git remote prune`.
From the remote man page:
> prune
> Deletes all stale tracking branches under <name>. These stale branches
> have already been removed from the remote repository referenced by
> <name>, but are still locally available in "remotes/<name>".
I'm unclear as to how this solves my problem. Consider the following:
$ git remote
a
b
c
$ git branch -a
a
b
c
remotes/a/branch
remotes/b/branch
remotes/c/branch
remotes/d/branch
$ git remote prune d
fatal: 'd' does not appear to be a git repository
fatal: The remote end hung up unexpectedly
$ git remote rm d
error: Could not remove config section 'remote.d'
I would like to get rid of the `remotes/d/branch` entry.
--
In Christ,
Timmy V.
http://burningones.com/
http://five.sentenc.es/ - Spend less time on e-mail
next prev parent reply other threads:[~2010-04-06 18:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-06 18:03 Getting rid of a stale remote? Tim Visher
2010-04-06 18:07 ` Ramkumar Ramachandra
2010-04-06 18:25 ` Tim Visher [this message]
2010-04-06 18:42 ` Jeff King
2010-04-09 2:08 ` Tim Visher
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=x2uc115fd3c1004061125i695f66bbi9f949ccc1958750@mail.gmail.com \
--to=tim.visher@gmail.com \
--cc=artagnon@gmail.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).