git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: [Newbie] How to *actually* get rid of remote tracking branch?
Date: Tue, 13 Nov 2007 15:53:52 +0100	[thread overview]
Message-ID: <fhcdpv$9u3$1@ger.gmane.org> (raw)
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:

> 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:
 

> $ 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

  reply	other threads:[~2007-11-13 15:03 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-13 14:25 [Newbie] How to *actually* get rid of remote tracking branch? Sergei Organov
2007-11-13 14:53 ` Jakub Narebski [this message]
2007-11-13 15:39   ` Sergei Organov
2007-11-13 16:01     ` Johannes Schindelin
2007-11-13 17:31       ` Sergei Organov
2007-11-13 18:21         ` Johannes Schindelin
2007-11-13 18:44           ` Sergei Organov
2007-11-17 16:56             ` Jan Hudec
2007-11-13 16:03     ` Jakub Narebski
2007-11-13 17:16       ` Steffen Prohaska
2007-11-13 17:42         ` Jakub Narebski
2007-11-13 17:58           ` osv
2007-11-13 18:17             ` Lars Hjemli
2007-11-13 18:59               ` Sergei Organov
2007-11-13 18:39             ` Steffen Prohaska
2007-11-17 19:12             ` Jan Hudec
2007-11-17 19:51               ` [PATCH] Improve description of git-branch -d and -D in man page Jan Hudec
2007-11-19  9:49                 ` Sergei Organov
2007-11-13 17:47         ` [Newbie] How to *actually* get rid of remote tracking branch? Sergei Organov
2007-11-13 20:01         ` Andreas Ericsson
2007-11-13 22:33           ` Andreas Ericsson
2007-11-13 22:42             ` Jakub Narebski
2007-11-13 23:05             ` J. Bruce Fields
2007-11-13 23:56             ` Junio C Hamano
2007-11-14  1:02               ` Andreas Ericsson
2007-11-14  5:48                 ` Steffen Prohaska
2007-11-13 17:40       ` Sergei Organov
2007-11-13 19:17         ` Jakub Narebski

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='fhcdpv$9u3$1@ger.gmane.org' \
    --to=jnareb@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).