Jakub Narebski <jnareb@xxxxxxxxx> writes:
> [Cc: Sergei Organov <osv@xxxxxxxxx>, git@xxxxxxxxxxxxxxx]
> Please CC git mailing list, git@xxxxxxxxxxxxxxx
>
> 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.
Sure, I've cloned git.git using rather recent git, so .git/config has:
fetch = +refs/heads/*:refs/remotes/origin/*
> 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.
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?
--
Sergei.
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
