From: Andy Parkins <andyparkins@gmail.com>
To: git@vger.kernel.org
Cc: Johannes Sixt <J.Sixt@eudaptics.com>
Subject: Re: How to get rid of tracking branch?
Date: Wed, 14 Feb 2007 13:35:37 +0000 [thread overview]
Message-ID: <200702141335.41165.andyparkins@gmail.com> (raw)
In-Reply-To: <45D30D8F.50261DB0@eudaptics.com>
On Wednesday 2007 February 14 13:24, Johannes Sixt wrote:
> Call me clueless, but how the heck do I get rid of a tracking remote
> branch? I've cloned a repo locally, but in the clone I don't want to
> track all the topic branches of the origin. But git branch -d keeps
> saying it doesn't find the remote branch:
$ git branch -r -d origin/repo-devel
I suffered the same thing a while ago :-)
Andy
--
Dr Andy Parkins, M Eng (hons), MIEE
andyparkins@gmail.com
next prev parent reply other threads:[~2007-02-14 13:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-14 13:24 How to get rid of tracking branch? Johannes Sixt
2007-02-14 13:35 ` Andy Parkins [this message]
2007-02-14 17:04 ` 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=200702141335.41165.andyparkins@gmail.com \
--to=andyparkins@gmail.com \
--cc=J.Sixt@eudaptics.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).