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

Re: Reading remote reflogs

From
Dennis Kaarsemaker <dennis@kaarsemaker.net>
Date
Mar 29, 2013, 22:56 UTC
Message-ID
<1364597780.30202.7.camel@localhost>
In-Reply-To
<7vd2uhn7u1.fsf@alter.siamese.dyndns.org>
On vr, 2013-03-29 at 15:45 -0700, Junio C Hamano wrote:
Show 8 quoted lines
> 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.

I was, as I tried the recipe below, though with a different repo. Must have goofed something up, as it works now. Thanks for the braincheck :)

That gives me a reasonable approximation of distinct pushes if I pull the mirror often enough. It's always going to be an approximation though, so the original question still stands.

-- 
Dennis Kaarsemaker
www.kaarsemaker.net
Previous: Junio C HamanoNext: Junio C Hamano
Message 3 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.