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

Re: Automatically remote prune

From
John Tapsell <johnflux@gmail.com>
Date
Nov 5, 2009, 08:05 UTC
Message-ID
<43d8ce650911050005l6d120cb0h374f3c04b3948b25@mail.gmail.com>
In-Reply-To
<7viqdpemki.fsf@alter.siamese.dyndns.org>
2009/11/5 Junio C Hamano <gitster@pobox.com>:
> John Tapsell <johnflux@gmail.com> writes:
> "what the benefits are to give this information _in the 'branch' output_"
> was what I meant.  From the part you omitted from my message:

I omitted it just because, imho, it's not what I 'care about'. I'm not trying to help advanced users (Users that _want_ to keep remotes/origin/* clean and users that _want_ to be careful to not lose commits are both advanced users, imho). I'm just interested in reducing confusion for non-advanced users. So either not-showing removed remote branches by default, or showing them but marking them as deleted.

> A better approach to please the first class of audience may be to
> introduce an option that tells fetch to cull tracking refs that are stale.
> Then "branch -r" output will not show stale refs and there is no place
> (nor need) to show [Deleted] labels.
If it's a non-default option, then it won't help the non-advanced users.
> Such an option won't be very useful for the second class of audience,
> though.  For them we would need something else, and it would likely be an
> enhancement to "git remote".

Which still leaves confusion when viewing "git branch -r" since they would show up there still.

John
Previous: Sitaram ChamartyNext: Junio C Hamano
Message 7 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.