git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: does git prune packs?
Date: Wed, 14 Sep 2005 11:14:46 -0400	[thread overview]
Message-ID: <43283E66.5080101@pobox.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0509140808010.26803@g5.osdl.org>

Linus Torvalds wrote:
> 
> On Wed, 14 Sep 2005, Jeff Garzik wrote:
> 
>>Does git-prune-packed eliminate packs that have been superceded by other 
>>packs?
> 
> 
> Nope. Pretty hard to do. Unless you just repack everything, at which point
> 
> 	git repack -a -d
> 
> will do the right thing.

I never repack, I just use your packs.

Easier on my hard disk, vastly reduces upload time (cable modem == slow 
uploads), since I can ssh to master.kernel.org and hardlink, and easier 
on kernel.org.

I'll remove the old packs manually.

Thanks,

	Jeff

  reply	other threads:[~2005-09-14 15:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-14 11:13 does git prune packs? Jeff Garzik
2005-09-14 15:08 ` Linus Torvalds
2005-09-14 15:14   ` Jeff Garzik [this message]
2005-09-14 15:30     ` Linus Torvalds

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=43283E66.5080101@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=torvalds@osdl.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).