All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Jeff King <peff@peff.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Do not run git-pack-refs by default for now from git-gc
Date: Tue, 13 Feb 2007 11:55:43 +0100 (CET)	[thread overview]
Message-ID: <Pine.LNX.4.63.0702131151520.22628@wbgn013.biozentrum.uni-wuerzburg.de> (raw)
In-Reply-To: <20070213102951.GA14903@coredump.intra.peff.net>

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

  reply	other threads:[~2007-02-13 10:56 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-13  9:27 linux-2.6.git/packed-refs??? Junio C Hamano
2007-02-13  9:48 ` [PATCH] Do not run git-pack-refs by default for now from git-gc Junio C Hamano
2007-02-13 10:03   ` Johannes Schindelin
2007-02-13 10:29     ` Jeff King
2007-02-13 10:55       ` Johannes Schindelin [this message]
2007-02-13 17:59         ` Junio C Hamano
2007-02-13 13:01       ` [PATCH] git-gc: run pack-refs by default unless the repo is bare Johannes Schindelin
2007-02-13 18:16 ` linux-2.6.git/packed-refs??? Theodore Tso
2007-02-13 18:41   ` linux-2.6.git/packed-refs??? Johannes Schindelin

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=Pine.LNX.4.63.0702131151520.22628@wbgn013.biozentrum.uni-wuerzburg.de \
    --to=johannes.schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=peff@peff.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 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.