From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: Nicolas Pitre <nico@cam.org>, Nix <nix@esperi.org.uk>,
Steven Grimm <koreth@midwinter.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: People unaware of the importance of "git gc"?
Date: Thu, 6 Sep 2007 16:54:56 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.64.0709061651550.28586@racer.site> (raw)
In-Reply-To: <7vr6lcj2zi.fsf@gitster.siamese.dyndns.org>
Hi,
On Wed, 5 Sep 2007, Junio C Hamano wrote:
> @@ -20,6 +20,7 @@ static const char builtin_gc_usage[] = "git-gc [--prune] [--aggressive]";
>
> static int pack_refs = 1;
> static int aggressive_window = -1;
> +static int gc_auto_threshold = 6700;
Please don't do that.
When you share objects with another git directory, git-gc --auto can get
rid of the objects when some objects go away in the referenced repository.
So we need _at least_ check gc.auto not being set in the repo when "git
clone --share"ing it (and fail otherwise).
My preferred way would be to set it in "git init" so that existing setups
are not affected, and put some big red message on top of the next release
notes that people might want to set gc.auto in their existing setups.
Ciao,
Dscho
next prev parent reply other threads:[~2007-09-06 15:55 UTC|newest]
Thread overview: 97+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-05 7:09 People unaware of the importance of "git gc"? Linus Torvalds
2007-09-05 7:21 ` Martin Langhoff
2007-09-05 7:37 ` Karl Hasselström
2007-09-05 7:30 ` Junio C Hamano
2007-09-05 7:26 ` Tomash Brechko
2007-09-05 8:13 ` Johan Herland
2007-09-05 8:39 ` Matthieu Moy
2007-09-05 8:41 ` Johan Herland
2007-09-05 8:47 ` David Kastrup
2007-09-05 8:51 ` Pierre Habouzit
2007-09-05 9:02 ` David Kastrup
2007-09-05 9:04 ` Matthieu Moy
2007-09-05 8:51 ` Wincent Colaiuta
2007-09-05 7:42 ` Pierre Habouzit
2007-09-05 8:16 ` Junio C Hamano
2007-09-05 8:50 ` Steven Grimm
[not found] ` <86ps0xcwxo.fsf@lola.quinscape.zz>
2007-09-05 9:07 ` Steven Grimm
2007-09-05 9:13 ` David Kastrup
2007-09-05 9:07 ` Junio C Hamano
2007-09-05 9:27 ` Martin Langhoff
2007-09-05 9:33 ` Matthieu Moy
2007-09-05 14:17 ` Johan De Messemaeker
2007-09-05 17:31 ` Matthieu Moy
2007-09-05 23:56 ` Jeff King
2007-09-05 9:13 ` David Kastrup
2007-09-05 9:14 ` Pierre Habouzit
2007-09-05 17:51 ` Nix
2007-09-05 18:14 ` Steven Grimm
2007-09-05 18:22 ` Nix
2007-09-05 18:54 ` Nicolas Pitre
2007-09-05 20:01 ` Junio C Hamano
2007-09-05 20:35 ` Nicolas Pitre
2007-09-05 21:14 ` Nix
2007-09-05 21:46 ` Junio C Hamano
2007-09-05 23:04 ` Nicolas Pitre
2007-09-05 23:42 ` Junio C Hamano
2007-09-06 0:27 ` Carlos Rica
2007-09-06 5:55 ` David Kastrup
2007-09-05 21:49 ` Junio C Hamano
2007-09-05 21:59 ` Invoke "git gc --auto" from commit, merge, am and rebase Junio C Hamano
2007-09-06 2:39 ` Shawn O. Pearce
2007-09-05 20:37 ` [PATCH] Invoke "git gc --auto" from "git add" and "git fetch" Junio C Hamano
[not found] ` <69b0c0350709051357ifa547aarfe3e0b36cf9be98f@mail.gmail.com>
2007-09-05 20:59 ` Fwd: " Govind Salinas
2007-09-06 12:02 ` Johannes Schindelin
2007-09-05 21:18 ` People unaware of the importance of "git gc"? Alex Riesen
2007-09-06 2:44 ` Russ Dill
2007-09-06 2:52 ` Shawn O. Pearce
2007-09-06 9:28 ` Andreas Ericsson
2007-09-06 2:45 ` Shawn O. Pearce
2007-09-06 2:49 ` Steven Grimm
2007-09-06 2:56 ` Shawn O. Pearce
2007-09-06 15:54 ` Johannes Schindelin [this message]
2007-09-06 17:49 ` Junio C Hamano
2007-09-06 18:15 ` Linus Torvalds
2007-09-06 18:29 ` Steven Grimm
2007-09-06 23:12 ` Subject: [PATCH] git-merge-pack Junio C Hamano
2007-09-06 23:35 ` Linus Torvalds
2007-09-07 0:51 ` Nicolas Pitre
2007-09-07 1:58 ` Junio C Hamano
2007-09-07 2:32 ` Nicolas Pitre
2007-09-07 4:07 ` Shawn O. Pearce
2007-09-07 4:43 ` Junio C Hamano
2007-09-08 9:50 ` [PATCH] make sha1_file.c::matches_pack_name() available to others Junio C Hamano
2007-09-08 10:01 ` [PATCH] pack-objects --repack-unpacked Junio C Hamano
2007-09-07 7:11 ` Subject: [PATCH] git-merge-pack Johannes Sixt
2007-09-07 7:34 ` Junio C Hamano
2007-09-07 7:24 ` Andy Parkins
2007-09-07 4:48 ` People unaware of the importance of "git gc"? Shawn O. Pearce
2007-09-07 10:12 ` Johannes Schindelin
2018-10-07 18:28 ` What's so special about objects/17/ ? Ævar Arnfjörð Bjarmason
2018-10-07 18:35 ` Johannes Sixt
2018-10-07 19:06 ` Ævar Arnfjörð Bjarmason
2018-10-07 22:39 ` Johannes Sixt
2018-10-08 0:54 ` Junio C Hamano
2018-10-07 19:46 ` Junio C Hamano
2018-10-07 20:07 ` Junio C Hamano
2018-10-08 19:17 ` Stefan Beller
2018-10-09 1:03 ` Junio C Hamano
2018-10-09 17:37 ` Stefan Beller
2018-10-10 1:10 ` Junio C Hamano
2018-10-10 19:08 ` Stefan Beller
2018-10-08 10:36 ` Ævar Arnfjörð Bjarmason
2018-10-09 1:07 ` Junio C Hamano
2018-10-09 17:40 ` Stefan Beller
2007-09-05 8:16 ` People unaware of the importance of "git gc"? David Kastrup
2007-09-05 16:47 ` Govind Salinas
2007-09-05 17:19 ` Carl Worth
2007-09-05 17:55 ` Jing Xue
2007-09-05 17:35 ` Steven Grimm
2007-09-05 18:28 ` Nix
2007-09-05 17:44 ` J. Bruce Fields
2007-09-05 18:46 ` Brandon Casey
2007-09-05 19:09 ` David Kastrup
2007-09-05 19:13 ` J. Bruce Fields
2007-09-05 19:43 ` David Kastrup
2007-09-05 19:20 ` Mike Hommey
2007-09-05 21:07 ` Alex Riesen
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.64.0709061651550.28586@racer.site \
--to=johannes.schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=koreth@midwinter.com \
--cc=nico@cam.org \
--cc=nix@esperi.org.uk \
--cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).