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

Automatically remote prune

From
John Tapsell <johnflux@gmail.com>
Date
Nov 4, 2009, 10:42 UTC
Message-ID
<43d8ce650911040242l44bbf87dm35494e04ce9039aa@mail.gmail.com>
Hi all,
  Is there any particular reason why "git update" doesn't
automatically remove remote branches that have been removed on the
server?  I keep getting questions about this from confused users.
  If there's strong resistance against that (there usually is for
changing any default behaviour), could we at least mark deleted
branches?
So maybe:

$> git branch -r origin/blah1 [Deleted] origin/blah2

(Some branches have been deleted on the remote server. Use "git remote prune origin" to remove these)

Or something.
John
Next: Junio C Hamano
Message 1 of 15 in “Automatically remote prune”
  1. John TapsellNov 4, 2009
  2. Junio C HamanoNov 4, 2009
  3. John TapsellNov 5, 2009
  4. Shawn O. PearceNov 5, 2009
  5. Junio C HamanoNov 5, 2009
  6. Sitaram ChamartyNov 5, 2009
  7. John TapsellNov 5, 2009
  8. Junio C HamanoNov 5, 2009
  9. Jay SoffianNov 5, 2009
  10. Petr BaudisNov 6, 2009
  11. Jay SoffianNov 6, 2009
  12. Petr BaudisNov 6, 2009
  13. Junio C HamanoNov 8, 2009
  14. Petr BaudisNov 6, 2009
  15. Dmitry PotapovNov 5, 2009

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.