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, 01:41 UTC
Message-ID
<43d8ce650911041741w4b39d137ha2a1529a15256d27@mail.gmail.com>
In-Reply-To
<7v639qi2un.fsf@alter.siamese.dyndns.org>
2009/11/5 Junio C Hamano <gitster@pobox.com>:
> John Tapsell <johnflux@gmail.com> writes:
> You could store necessary information somewhere else when you contacted
> the remote the last time, but we need to consider what the benefits are to
> give this information in the first place.

We already get all this information on a "git fetch", no? And then promptly discard it. Surely when we do "git fetch" . So I'm talking about just not ignoring the information we get from git fetch, but present that information to the user.

John
Previous: Junio C HamanoNext: Shawn O. Pearce
Message 3 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.