From: Matthieu Moy <Matthieu.Moy@imag.fr>
To: Nicolas Pitre <nico@cam.org>
Cc: Brandon Casey <casey@nrlssc.navy.mil>, Jeff King <peff@peff.net>,
John Dlugosz <JDlugosz@TradeStation.com>,
git@vger.kernel.org
Subject: Re: dangling commits and blobs: is this normal?
Date: Wed, 22 Apr 2009 20:15:56 +0200 [thread overview]
Message-ID: <vpqws9cd06b.fsf@bauges.imag.fr> (raw)
In-Reply-To: <alpine.LFD.2.00.0904221331450.6741@xanadu.home> (Nicolas Pitre's message of "Wed\, 22 Apr 2009 13\:39\:21 -0400 \(EDT\)")
Nicolas Pitre <nico@cam.org> writes:
> Why so? Having fewer packs is always a good thing. Having only one
> pack is of course the optimal situation.
Good and optimal wrt Git, but not wrt an incremental backup system for
example. I have a "git gc" running daily in a cron job in each of my
repositories, but to be nice with my sysadmin, I don't want to rewrite
tens of megabytes of data each night just because I commited a 2 lines
patch somewhere.
--
Matthieu
next prev parent reply other threads:[~2009-04-22 19:00 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-21 21:46 dangling commits and blobs: is this normal? John Dlugosz
2009-04-22 15:27 ` Jeff King
2009-04-22 16:53 ` Brandon Casey
2009-04-22 17:39 ` Nicolas Pitre
2009-04-22 18:15 ` Matthieu Moy [this message]
2009-04-22 19:08 ` Jeff King
2009-04-22 19:45 ` Brandon Casey
2009-04-22 19:58 ` Jeff King
2009-04-22 20:07 ` Nicolas Pitre
2009-04-23 11:51 ` Matthieu Moy
2009-04-22 19:14 ` Nicolas Pitre
2009-04-22 19:26 ` Brandon Casey
2009-04-22 20:00 ` Nicolas Pitre
2009-04-22 20:05 ` Jeff King
2009-04-22 20:11 ` Nicolas Pitre
2009-04-23 17:43 ` Geert Bosch
2009-04-23 17:56 ` Shawn O. Pearce
2009-04-23 18:10 ` Geert Bosch
2009-04-23 18:17 ` Matthias Andree
2009-04-23 18:51 ` Nicolas Pitre
2009-04-22 20:15 ` John Dlugosz
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=vpqws9cd06b.fsf@bauges.imag.fr \
--to=matthieu.moy@imag.fr \
--cc=JDlugosz@TradeStation.com \
--cc=casey@nrlssc.navy.mil \
--cc=git@vger.kernel.org \
--cc=nico@cam.org \
--cc=peff@peff.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.