git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [Newbie] How to *actually* get rid of remote tracking branch?

From
Jakub Narebski <jnareb@gmail.com>
Date
Nov 13, 2007, 16:03 UTC
Message-ID
<200711131703.16357.jnareb@gmail.com>
In-Reply-To
<87ve86889o.fsf@osv.gnss.ru>
Sergei Organov <osv@javad.com> wrote:
> Jakub Narebski <jnareb@gmail.com> writes:
>> Sergei Organov wrote:
Show 6 quoted lines
>>> 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 22 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. 
> 
> Sure, I've cloned git.git using rather recent git, so .git/config has:
> 
>       fetch = +refs/heads/*:refs/remotes/origin/*
[...] 
> Isn't "git branch -d -r" supposed to do whatever magic is required to
> get rid of the remote branch? Currently it seems like a bug introduced
> by addition of wildcards refspecs, right?

No, the '-r' part translates 'pu' into 'refs/remotes/origin/pu', and the '-d' option removes branch locally. It is meant I think to remove tracking of branches which were dropped in remote, as I think that wildcard refspec does create new branches, but do not delete dropped branches.

So I'm not sure if it is a bug, misfeature or a feature.
Can anyone better versed in wildcard refspecs speak up, please?
-- 
Jakub Narebski
Poland
Previous: Jan HudecNext: Steffen Prohaska
Message 9 of 28 in “[Newbie] How to *actually* get rid of remote tracking branch?”
  1. Sergei OrganovNov 13, 2007
  2. Jakub NarebskiNov 13, 2007
  3. Sergei OrganovNov 13, 2007
  4. Johannes SchindelinNov 13, 2007
  5. Sergei OrganovNov 13, 2007
  6. Johannes SchindelinNov 13, 2007
  7. Sergei OrganovNov 13, 2007
  8. Jan HudecNov 17, 2007
  9. Jakub NarebskiNov 13, 2007
  10. Steffen ProhaskaNov 13, 2007
  11. Jakub NarebskiNov 13, 2007
  12. osv@javad.comNov 13, 2007
  13. Lars HjemliNov 13, 2007
  14. Sergei OrganovNov 13, 2007
  15. Steffen ProhaskaNov 13, 2007
  16. Jan HudecNov 17, 2007
  17. Improve description of git-branch -d and -D in man page.Jan Hudec, Nov 17, 2007
  18. Sergei OrganovNov 19, 2007
  19. Sergei OrganovNov 13, 2007
  20. Andreas EricssonNov 13, 2007
  21. Andreas EricssonNov 13, 2007
  22. Jakub NarebskiNov 13, 2007
  23. J. Bruce FieldsNov 13, 2007
  24. Junio C HamanoNov 13, 2007
  25. Andreas EricssonNov 14, 2007
  26. Steffen ProhaskaNov 14, 2007
  27. Sergei OrganovNov 13, 2007
  28. Jakub NarebskiNov 13, 2007

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.