Re: [PATCH v2] gc: call "prune --expire 2.weeks.ago" by default

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

 



Hi,

On Wed, 12 Mar 2008, Jakub Narebski wrote:

> Brandon Casey <casey@xxxxxxxxxxxxxxx> writes:
> 
> > Is 'git-gc --prune' still useful to end users when those in-the-know 
> > can use git-prune when they really want all loose unreferenced objects 
> > to be removed?
> 
> It is one command less to remember (just like with "git tag --verify" 
> and "git verify-tag"), so I'm all for "git gc --prune" to remain.

I don't care one way or the other.

> > Also, what about clones created with --shared or --reference? Should 
> > there be a way to disable this functionality? gc.pruneExpire never
> 
> That would be nice.

Okay, so I just remove the !approxidate() check.  Then, "gc.pruneExpire = 
never" should work as you expect it to.

Ciao,
Dscho

--
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]

  Powered by Linux