From: Erik Faye-Lund <kusmabite@googlemail.com>
To: SungHyun Nam <goweol@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: cannot remove remote branch name
Date: Tue, 5 Jan 2010 02:59:37 +0100 [thread overview]
Message-ID: <40aa078e1001041759p22657d0cwe094a348dca32842@mail.gmail.com> (raw)
In-Reply-To: <hhu694$3v9$1@ger.gmane.org>
On Tue, Jan 5, 2010 at 2:57 AM, SungHyun Nam <goweol@gmail.com> wrote:
> Hello,
>
> How I can remove remote branch name if it already removed
> in remote side?
>
> $ git branch -a
> * master
> remotes/origin/HEAD -> origin/master
> remotes/origin/master
> remotes/origin/test
> $ git branch -D -r test
> error: remote branch 'test' not found.
> $ git branch -D -r remotes/origin/test
> error: remote branch 'remotes/origin/test' not found.
> $ git branch -D remotes/origin/test
> error: branch 'remotes/origin/test' not found.
>
> The 'remotes/origin/test' was removed in remote side.
>
$ git remote prune origin
--
Erik "kusma" Faye-Lund
next prev parent reply other threads:[~2010-01-05 1:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-05 1:57 cannot remove remote branch name SungHyun Nam
2010-01-05 1:59 ` Erik Faye-Lund [this message]
2010-01-05 2:18 ` Junio C Hamano
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=40aa078e1001041759p22657d0cwe094a348dca32842@mail.gmail.com \
--to=kusmabite@googlemail.com \
--cc=git@vger.kernel.org \
--cc=goweol@gmail.com \
--cc=kusmabite@gmail.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