From: Jeff King <peff@peff.net>
To: Jakub Narebski <jnareb@gmail.com>
Cc: Johan Herland <johan@herland.net>,
Michael J Gruber <git@drmicha.warpmail.net>,
git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH 2/2] refs.c: Write reflogs for notes just like for branch heads
Date: Thu, 1 Apr 2010 20:16:41 -0400 [thread overview]
Message-ID: <20100402001640.GH16462@coredump.intra.peff.net> (raw)
In-Reply-To: <m3mxxpipqw.fsf@localhost.localdomain>
On Tue, Mar 30, 2010 at 12:18:16PM -0700, Jakub Narebski wrote:
> > > 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
prev parent reply other threads:[~2010-04-02 0:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-29 13:05 [PATCH 1/2] t3301-notes: Test the creation of reflog entries Michael J Gruber
2010-03-29 13:05 ` [PATCH 2/2] refs.c: Write reflogs for notes just like for branch heads Michael J Gruber
2010-03-29 14:25 ` Johan Herland
2010-03-30 17:19 ` Jeff King
2010-03-30 18:00 ` Johan Herland
2010-03-30 19:18 ` Jakub Narebski
2010-04-02 0:16 ` Jeff King [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100402001640.GH16462@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jnareb@gmail.com \
--cc=johan@herland.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).