Re: [Newbie] How to *actually* get rid of remote tracking branch?
- From
Jakub Narebski <jnareb@gmail.com>
- Date
- Nov 13, 2007, 14:53 UTC
- Message-ID
- <fhcdpv$9u3$1@ger.gmane.org>
- In-Reply-To
- <874pfq9q8s.fsf@osv.gnss.ru>
[Cc: Sergei Organov <osv@javad.com>, git@vger.kernel.org] Please CC git mailing list, git@vger.kernel.org
Sergei Organov wrote:
Show 8 quoted lines
> Hello, > > I want to get rid of origin/pu remote tracking branch. What do I do? I > RTFM git-branch. What does it suggest? > > git branch -d -r origin/pu > > So far so good. However, it doesn't seem to work in practice:
Show 12 quoted lines
> $ git branch -d -r origin/pu > Deleted remote branch origin/pu. > $ git remote show origin > * remote origin > URL: git://git.kernel.org/pub/scm/git/git.git > Remote branch(es) merged with 'git pull' while on branch master > master > New remote branches (next fetch will store in remotes/origin) > pu > ^^^^^^^^^^^^^^^^^^^ What??? > Tracked remote branches > html maint man master next todo
Check out what do you have in .git/config file, in the [remote "origin"] section. Most probably (if you cloned this repository using new enough git) you have wildcard refspec there, which means that git would pick all new branches when fetching / pulling from given repository. The wildcard refspec is not documented adequately, so I'm not sure if adding
fetch = !refs/heads/pu
would help, or do you have to replace wildcard refspec by explicit list of branches you want to fetch.
-- Jakub Narebski Warsaw, Poland ShadeHawk on #git