From: Junio C Hamano <junkio@cox.net>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Create 'git gc' to perform common maintenance operations.
Date: Tue, 26 Dec 2006 23:46:52 -0800 [thread overview]
Message-ID: <7vr6ul93wz.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <20061227071759.GA23057@spearce.org> (Shawn O. Pearce's message of "Wed, 27 Dec 2006 02:17:59 -0500")
"Shawn O. Pearce" <spearce@spearce.org> writes:
> +The optional configuration variable 'gc.reflogExpireUnreachable'
> +can be set to indicate how long historical reflog entries which
> +are not part of the current branch should remain available in
> +this repository. These types of entries are generally created as
> +a result of using `git commit \--amend` or `git rebase` and are the
> +commits prior to the amend or rebase occuring. Since these changes
> +are not part of the current project most users will want to expire
> +them sooner. This option defaults to '60 days'.
Should I update the default expire-unreachable in builtin-reflog
to match 60 days?
next prev parent reply other threads:[~2006-12-27 7:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-27 7:17 [PATCH] Create 'git gc' to perform common maintenance operations Shawn O. Pearce
2006-12-27 7:46 ` Junio C Hamano [this message]
2006-12-27 7:53 ` Shawn Pearce
2006-12-27 8:26 ` Junio C Hamano
2006-12-27 8:33 ` Shawn Pearce
2006-12-27 9:10 ` Junio C Hamano
2006-12-27 13:11 ` Martin Waitz
2006-12-27 18:46 ` Junio C Hamano
-- strict thread matches above, loose matches on Subject: below --
2006-12-27 7:05 Shawn O. Pearce
2006-12-27 7:12 ` Linus Torvalds
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=7vr6ul93wz.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=spearce@spearce.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.