git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: DigitalPig <digitalpiglee@gmail.com>
To: git@vger.kernel.org
Subject: What is the difference between git-gc, git-repack and git-prune?
Date: Tue, 06 May 2008 22:44:11 -0400	[thread overview]
Message-ID: <873aoux284.fsf@gmail.com> (raw)

Hi!

For git-prune, according to the manual, it will delete all the dangling
objects. So it is easy to understand. However, in the git-gc manpage,
there is another option named "--prune". Does that make git-gc do the
same thing as git-prune?

And manpage of git-gc says it cleans unnecessary files and compresses
the objects, and git-repack also compresses the objects too. Are there
any difference between these two operations? Or do I need to invoke
git-repack after running git-gc? Thanks!


Zhenqing

-- 
DigitalPig
E-mail: digitalpiglee AT gmail DOT com
ALL WE SEEN IS ILLUSION.

*Fudan University Macromoleculer Science Forum*
http://fudanmacro.com

             reply	other threads:[~2008-05-07  2:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-07  2:44 DigitalPig [this message]
2008-05-07  2:53 ` What is the difference between git-gc, git-repack and git-prune? Avery Pennarun

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=873aoux284.fsf@gmail.com \
    --to=digitalpiglee@gmail.com \
    --cc=git@vger.kernel.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).