Our team creates topic branches, then when they are ready rebases them and merges them into our testing branch and then deletes the old topic branch.
Apparently git pull and fetch don't automatically trim the list of branches that it thinks origin has. On my local checkout a branch -a shows 20 or so branches that have since been deleted, but I can't get them to go away. Is there any facility to force it to go out and verify it's list against the real origin, instead of deleting the whole checkout and recloning? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Git for human beings" group. To post to this group, send email to git-users@googlegroups.com To unsubscribe from this group, send email to git-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/git-users?hl=en -~----------~----~----~----~------~----~------~--~---
