From: Sam Vilain <sam@vilain.net>
To: git@vger.kernel.org
Subject: is git-unpack-objects now redundant for 'git-push' and friends?
Date: Wed, 11 Oct 2006 02:23:52 +1300 [thread overview]
Message-ID: <452B9EE8.5020702@vilain.net> (raw)
When pushing or pulling to/from a repository, why unpack the objects?
Why not just fsck and then throw the pack into $GIT_DIR/objects/pack?
If you're pushing the entire repository, for instance, currently you
might create 10,000's of files, which will just be thrown away later
when you `git-repack -d'.
I suspect that this was never changed, because there never used to be
more than one packfile allowed, correct?
If the server *does* send us duplicates of objects we already have for
some reason, well that's what `git-repack -a -d' is for.
I'm just wondering if there are any good reasons to do this any more.
Sam.
next reply other threads:[~2006-10-10 13:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-10 13:23 Sam Vilain [this message]
2006-10-10 16:14 ` is git-unpack-objects now redundant for 'git-push' and friends? Shawn Pearce
2006-10-10 17:44 ` Junio C Hamano
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=452B9EE8.5020702@vilain.net \
--to=sam@vilain.net \
--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 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.