Re: [PATCH] Do not run git-pack-refs by default for now from git-gc

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

 



Hi,

On Tue, 13 Feb 2007, Jeff King wrote:

> On Tue, Feb 13, 2007 at 11:03:32AM +0100, Johannes Schindelin wrote:
> 
> > It seems to me that the reason are dumb transports, which are very 
> > likely to run only from bare repositories. How about checking for a 
> > bare repository explicitely, and only if it _is_ bare, check for 
> > gc.packrefs, too?
> 
> The way you have stated it, I think we will get a lot of "I set 
> gc.packrefs, but it doesn't do anything!" complaints. I think a 
> tri-state "yes/no/notbare" defaulting to "notbare" makes more sense. But 
> maybe you meant the other way around in the first place.

No, I meant it as you understood it. But your solution is evidently way 
more elegant.

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]