From: Junio C Hamano <junkio@cox.net>
To: "Lukas Sandström" <lukass@etek.chalmers.se>
Cc: git@vger.kernel.org
Subject: Re: [QUESTION] Access to a huge GIT repository.
Date: Sat, 19 Nov 2005 12:42:01 -0800 [thread overview]
Message-ID: <7vu0e84bfq.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <437F1E67.8020302@etek.chalmers.se> (Lukas Sandström's message of "Sat, 19 Nov 2005 13:45:27 +0100")
Lukas Sandström <lukass@etek.chalmers.se> writes:
> The "git-repack -a -d" case is fixed in Junios master, and I have sent out
> a patch which lets you pipe git-fsck-objects --full --unreachable to
> git-pack-redundant in the other cases, so the problem should hopefully
> be resolved shortly.
After thinking a bit about it, I tend to agree with what Linus
said, and would vote for the simplicity of the older way. From
usage point of view, git-repack is primarily about repacking,
and the -d option is a funny exception applicable to -a case,
only because it is so obvious (i.e. after repacking everything
into one, it is obvious any other packs are unneeded). We might
even want to make the "-a" flag to imply "-a -d" there.
next prev parent reply other threads:[~2005-11-19 20:42 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-16 12:24 [QUESTION] Access to a huge GIT repository Franck
2005-11-16 16:46 ` Linus Torvalds
2005-11-17 10:36 ` Franck
2005-11-17 16:23 ` Linus Torvalds
2005-11-17 21:47 ` Franck
2005-11-17 22:44 ` Linus Torvalds
2005-11-19 12:23 ` Franck
2005-11-19 12:45 ` Lukas Sandström
2005-11-19 20:42 ` Junio C Hamano [this message]
2005-11-19 17:56 ` Linus Torvalds
2005-11-19 19:52 ` Junio C Hamano
2005-11-21 20:11 ` Franck
2005-11-21 20:45 ` Junio C Hamano
2005-11-22 9:22 ` Franck
2005-11-22 9:50 ` Junio C Hamano
2005-11-22 10:40 ` Franck
2005-11-22 17:06 ` Junio C Hamano
2005-11-22 19:10 ` Franck
2005-11-16 18:24 ` Junio C Hamano
2005-11-16 20:01 ` Martin Langhoff
2005-11-16 20:10 ` Linus Torvalds
2005-11-16 20:35 ` Junio C Hamano
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=7vu0e84bfq.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=lukass@etek.chalmers.se \
/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).