git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ralf Wildenhues <Ralf.Wildenhues@gmx.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: integrity of a repository
Date: Sun, 16 Mar 2008 11:09:52 +0100	[thread overview]
Message-ID: <20080316100952.GC32394@ins.uni-bonn.de> (raw)
In-Reply-To: <7v8x0jkv8t.fsf@gitster.siamese.dyndns.org>

* Junio C Hamano wrote on Sun, Mar 16, 2008 at 08:01:38AM CET:
> Ralf Wildenhues <Ralf.Wildenhues@gmx.de> writes:
> 
> > OK.  Now, is there a way to quickly ensure that a repository is in a
> > pruned state, short of running 'git gc --prune'?
> 
> "git fsck --full"?

Ahh, good.  Thanks!
Ralf

      reply	other threads:[~2008-03-16 10:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-15 13:26 integrity of a repository Ralf Wildenhues
2008-03-16  3:54 ` Junio C Hamano
2008-03-16  6:32   ` Ralf Wildenhues
2008-03-16  7:01     ` Junio C Hamano
2008-03-16 10:09       ` Ralf Wildenhues [this message]

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=20080316100952.GC32394@ins.uni-bonn.de \
    --to=ralf.wildenhues@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.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).