[Bug 1321836] [NEW] "git remote remove" does not always remove remote branches
Rolf Leggewie
1321836 at bugs.launchpad.net
Wed May 21 17:05:14 UTC 2014
Public bug reported:
In my local polipo git directory I remove an old entry to where upstream
was doing the work (can't remember the URL, upstream now hosts on
github). The command I used was "git remote remove jussieu" and that
went fine. Yet, I still have all remote branches listed in "git branch
-av".
$ git branch -av|grep jus
remotes/jussieu/1.0.4-branch 12b9179 Don't revalidate objects >= CHUNK_SIZE that aren't in disk cache.
remotes/jussieu/master ec4d638 Cache to disk even when "HTTP://" scheme is uppercase
remotes/jussieu/polipo-chrisd b92db57 Add -fno-strict-aliasing to prevent compile warnings on some systems.
This is on a trusty installation with git 1:1.9.1-1.
** Affects: git (Ubuntu)
Importance: Undecided
Status: New
** Tags: trusty
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to git in Ubuntu.
https://bugs.launchpad.net/bugs/1321836
Title:
"git remote remove" does not always remove remote branches
Status in “git” package in Ubuntu:
New
Bug description:
In my local polipo git directory I remove an old entry to where
upstream was doing the work (can't remember the URL, upstream now
hosts on github). The command I used was "git remote remove jussieu"
and that went fine. Yet, I still have all remote branches listed in
"git branch -av".
$ git branch -av|grep jus
remotes/jussieu/1.0.4-branch 12b9179 Don't revalidate objects >= CHUNK_SIZE that aren't in disk cache.
remotes/jussieu/master ec4d638 Cache to disk even when "HTTP://" scheme is uppercase
remotes/jussieu/polipo-chrisd b92db57 Add -fno-strict-aliasing to prevent compile warnings on some systems.
This is on a trusty installation with git 1:1.9.1-1.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/git/+bug/1321836/+subscriptions
More information about the foundations-bugs
mailing list