From: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Alex Riesen <raa.lkml@gmail.com>,
Junio C Hamano <gitster@pobox.com>,
Johannes Sixt <j.sixt@viscovery.net>,
Sergio Callegari <sergio.callegari@gmail.com>,
git@vger.kernel.org
Subject: Re: git fsck not identifying corrupted packs
Date: Tue, 20 Oct 2009 13:56:53 +0200 [thread overview]
Message-ID: <vpq1vkygtx6.fsf@bauges.imag.fr> (raw)
In-Reply-To: <alpine.DEB.1.00.0910201221250.4985@pacific.mpi-cbg.de> (Johannes Schindelin's message of "Tue\, 20 Oct 2009 12\:22\:40 +0200 \(CEST\)")
Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
> Hi,
>
> On Tue, 20 Oct 2009, Alex Riesen wrote:
>
>> On Tue, Oct 20, 2009 at 08:45, Junio C Hamano <gitster@pobox.com> wrote:
>> > Matthieu Moy <Matthieu.Moy@grenoble-inp.fr> writes:
>> >>> It probably is also a good idea to add a "--loose" option that does what
>> >>> "fsck" currently does without "--full". It is a good name
>>
>> --no-full works
>
> It works. Technically. For human users, though, --loose-objects-only
> (with a shortcut "--loose") would be better.
OTOH, the advantage of "--no-full" is that it's compatible with
existing Git versions. If I learn Git 1.6.6 with --no-full, and use it
in a script, then my stript works also with older Gits.
But anyway, I think very few people are actually interested in "git
--no-full" (or call it whatever you like), so I don't think this is
very important.
--
Matthieu Moy
http://www-verimag.imag.fr/~moy/
next prev parent reply other threads:[~2009-10-20 12:01 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-19 7:56 git fsck not identifying corrupted packs Sergio Callegari
2009-10-19 9:11 ` Johannes Sixt
2009-10-19 10:04 ` Johannes Schindelin
2009-10-19 19:03 ` Junio C Hamano
2009-10-19 19:27 ` Wesley J. Landaker
2009-10-20 15:41 ` Robin Rosenberg
2009-10-20 16:20 ` Wesley J. Landaker
2009-10-20 6:26 ` Matthieu Moy
2009-10-20 6:45 ` Junio C Hamano
2009-10-20 9:25 ` Alex Riesen
2009-10-20 10:22 ` Johannes Schindelin
2009-10-20 11:56 ` Matthieu Moy [this message]
2009-10-20 18:46 ` [RFC/PATCH] fsck: default to "git fsck --full" Junio C Hamano
2009-10-20 19:00 ` Nicolas Pitre
2009-10-20 19:11 ` Junio C Hamano
2009-10-20 18:39 ` git fsck not identifying corrupted packs Nicolas Pitre
2009-10-20 20:49 ` Alex Riesen
2009-10-19 10:56 ` Sergio Callegari
2009-10-19 19:07 ` Wesley J. Landaker
2009-10-20 6:24 ` Matthieu Moy
2009-10-19 18:36 ` Gabor Gombas
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=vpq1vkygtx6.fsf@bauges.imag.fr \
--to=matthieu.moy@grenoble-inp.fr \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=j.sixt@viscovery.net \
--cc=raa.lkml@gmail.com \
--cc=sergio.callegari@gmail.com \
/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).