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

thoughts on setting core.logAllRefUpdates default true for bare repos

From
Sitaram Chamarty <sitaramc@gmail.com>
Date
Nov 4, 2009, 12:55 UTC
Message-ID
<slrnhf2uep.7d3.sitaramc@sitaramc.homelinux.net>

It seems to me an accidental push -f would cause some trouble on a bare repo, and would usually require a bit of grubbing around among the unreachable commits looking for the right one.

What would be the downsides (other than some objects hanging around far longer, i.e., space issues) of setting the config variable core.logAllRefUpdates to be default true on bare repos.

Next: Johannes Schindelin
Message 1 of 11 in “thoughts on setting core.logAllRefUpdates default true for bare repos”
  1. Sitaram ChamartyNov 4, 2009
  2. Johannes SchindelinNov 4, 2009
  3. Sitaram ChamartyNov 4, 2009
  4. demerphqNov 4, 2009
  5. Nicolas SebrechtNov 4, 2009
  6. Sverre RabbelierNov 4, 2009
  7. Sitaram ChamartyNov 5, 2009
  8. Matthieu MoyNov 4, 2009
  9. Junio C HamanoNov 4, 2009
  10. Matthieu MoyNov 4, 2009
  11. Sitaram ChamartyNov 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.