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

Re: [PATCH] Documentation: clearly specify what refs are honored by core.logAllRefUpdates

From
Junio C Hamano <gitster@pobox.com>
Date
Jul 11, 2011, 21:24 UTC
Message-ID
<7vaackbjed.fsf@alter.siamese.dyndns.org>
In-Reply-To
<CAKPyHN3aef5MQh+rv4O07vrVbzziTj+==2H-hKM1XwUwCOqq6Q@mail.gmail.com>
Bert Wesarg <bert.wesarg@googlemail.com> writes:
> The question is: should the user be able to disable logging of the
> hard-coded values. With your examples that would be possible. But I
> think we should not allow that.

You have to justify that position. I do not see any reason to forbid myself from declining reflog for refs/remotes/ while still logging the updates to my refs/heads/.

Previous: Bert WesargNext: Michael Haggerty
Message 4 of 6 in “Documentation: clearly specify what refs are honored by core.logAllRefUpdates”
  1. Documentation: clearly specify what refs are honored by core.logAllRefUpdatesBert Wesarg, Jul 11, 2011
  2. Junio C HamanoJul 11, 2011
  3. Bert WesargJul 11, 2011
  4. Junio C HamanoJul 11, 2011
  5. Michael HaggertyJul 12, 2011
  6. Bert WesargJul 12, 2011

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.