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

Re: Reading remote reflogs

From
Junio C Hamano <gitster@pobox.com>
Date
Mar 29, 2013, 22:45 UTC
Message-ID
<7vd2uhn7u1.fsf@alter.siamese.dyndns.org>
In-Reply-To
<1364595928.30202.4.camel@localhost>
Dennis Kaarsemaker <dennis@kaarsemaker.net> writes:
> ... Mirrored repositories don't
> maintain a reflog, even with core.logAllRefUpdates = true,...

Are you sure about this? When log_all_ref_updates is not set, by default we do not log for bare repositories, but other than that, we do not do anything special with respect to reflogs.

	$ (cd .. && git clone --no-local --mirror git.git victim)
        $ git checkout next
        $ EDITOR=: git commit --amend
        $ cd ../victim
	$ git config core.logallrefupdates true
	$ git fetch
        $ find logs
	logs
        logs/HEAD
        logs/refs
        logs/refs/heads
        logs/refs/heads/next

It seems to record how a branch at its origin was updated just fine, at least to me.

Previous: Dennis KaarsemakerNext: Dennis Kaarsemaker
Message 2 of 5 in “Reading remote reflogs”
  1. Dennis KaarsemakerMar 29, 2013
  2. Junio C HamanoMar 29, 2013
  3. Dennis KaarsemakerMar 29, 2013
  4. Junio C HamanoMar 29, 2013
  5. Dennis KaarsemakerMar 30, 2013

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.