Re: [PATCH] Create 'git gc' to perform common maintenance operations.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Shawn Pearce <spearce@xxxxxxxxxxx> writes:

> Junio C Hamano <junkio@xxxxxxx> wrote:
>> Shawn Pearce <spearce@xxxxxxxxxxx> writes:
>> 
>> > I don't care either way.  60 days may be too long for some users,
>> > but for others it may be nice to have.  I think the two defaults
>> > should match just because.  Feel free to edit my patch before
>> > applying to be whatever 'git-reflog expire' uses if you want.
>> 
>> I think the built-in git-reflog should be updated to honor the
>> configuration in the absense of command line options; if we do
>> that git-gc.sh does not even have to call repo-config anymore.
>
> Sure, but then maybe the configuration options shouldn't be
> 'gc.reflog*' but instead 'reflog.*'.

Actually I think gc.reflog, gc.rerere and friends make more
sense.  In other words, I think it is better to match the
configuration group to what the end user primarily sees, which
is "gc"; "reflog expire" and "rerere gc" are implementation
details of it.


-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]