On Mar 09, 2017, at 02:30 PM, R. David Murray wrote: >If it isn't already in the devguide (I have to admit I haven't really >read the new guide yet), once you end up pulling one of those branches >into your remotes, it will stay there until you do: > > git remote prune <upstream> > >The above will delete any local copies of branches that have been >deleted in <upstream>.
It may be equivalent, but I generally do `git fetch --prune --all` to get rid of local copies of deleted branches in all remotes. Then `git branch -d` to remove any local tracking branches of pruned branches, e.g. if one of my branches has been merged and deleted on GitHub. Not to start an editor war, but *if* you are an Emacs user, I highly recommend magit for dealing with git repositories. It's completely changed my opinion of git for the better. I no longer complain that much about git's command line --'cause I barely use it! That, and git bash completion which you can probably get from your Linux distro if you use such a thing, has actually made git pretty indispensable for me now. (Brett may be shocked given my previous advocacy for alternatives. ;) Maybe we should have a git tips and tricks BoF at Pycon. I'd love to hear about ways other people use git, especially on the CPython repo. Cheers, -Barry _______________________________________________ python-committers mailing list python-committers@python.org https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/
