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

Re: [PATCH 2/2] refs.c: Write reflogs for notes just like for branch heads

From
Jeff King <peff@peff.net>
Date
Apr 2, 2010, 00:16 UTC
Message-ID
<20100402001640.GH16462@coredump.intra.peff.net>
In-Reply-To
<m3mxxpipqw.fsf@localhost.localdomain>
On Tue, Mar 30, 2010 at 12:18:16PM -0700, Jakub Narebski wrote:
Show 15 quoted lines
> > > I like the idea of having a reflog, just because you could use it to
> > > salvage an old cache if you were playing around with your helper's
> > > options (or debugging your helper :) ). The usual 90-day expiration
> > > time is perhaps too long, though.
> > 
> > Yes, 90 days as a default might be excessive, but you can always 
> > override it with a "git gc --prune=now"...
> 
> You can always set different expire time for notes by using
> 
>   [gc "refs/notes"]
>         reflogExpire = 7 # days, I suppose
> 
> Which is not documented (I have found it in RelNotes-1.6.0.txt).  
> Oh well...

Thanks, I didn't know about that feature. I just posted my series without dealing with the reflogs at all, but I think it may be sensible to drop the default for "refs/notes/textconv" in a followup patch.

-Peff
Previous: Jakub Narebski
Message 7 of 7 in “t3301-notes: Test the creation of reflog entries”
  1. 1/2 t3301-notes: Test the creation of reflog entriesMichael J Gruber, Mar 29, 2010
  2. 2/2 refs.c: Write reflogs for notes just like for branch headsMichael J Gruber, Mar 29, 2010
  3. Johan HerlandMar 29, 2010
  4. Jeff KingMar 30, 2010
  5. Johan HerlandMar 30, 2010
  6. Jakub NarebskiMar 30, 2010
  7. Jeff KingApr 2, 2010

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.