From: "Luck, Tony" <tony.luck@intel.com>
To: git@vger.kernel.org
Subject: git push sends more objects than it needs to
Date: Mon, 31 Oct 2005 10:23:55 -0800 [thread overview]
Message-ID: <20051031182355.GA7368@agluck-lia64.sc.intel.com> (raw)
I just pulled from Linus' Linux repository ... and my
wrapper script alerted me to the fact that he had just
re-packed.
So, I logged into kernel.org and linked the new packfiles
across to my repo there, and did a "git prune-packed" to
clean away all the unneeded unpacked objects.
Back on my local box I merged all the new stuff that
had been pulled into my "release" and "test" branches.
(just a fast-forward for the release branch).
Next I used "scp" to copy Linus' new pack files to my
local objects/pack ... and ran git prune packed here.
Finally, after making sure that release and test
branches still built with all the new stuff I did
a "git push" to update my kernel repo. I saw this:
updating 'refs/heads/test'
from 0711c558ff3cf4d1e498a9686f4d8ce48aa8d79f
to 2e488d3f8f299eb0ed826055bc30003e2c27d909
updating 'refs/heads/release'
from 8a212ab6b8a4ccc6f3c3d1beba5f92655c576404
to 581c1b14394aee60aff46ea67d05483261ed6527
Packing 10785 objects
Unpacking 10785 objects
100% (10785/10785) done
refs/heads/test: 0711c558ff3cf4d1e498a9686f4d8ce48aa8d79f -> 2e488d3f8f299eb0ed826055bc30003e2c27d909
refs/heads/release: 8a212ab6b8a4ccc6f3c3d1beba5f92655c576404 -> 581c1b14394aee60aff46ea67d05483261ed6527
Now the "unpack" on kernel.org did the right thing and noticed
that over 9000 of the objects were already in the packfile. But
I wonder if it couldn't have been smarter and not sent them?
Or am I just subverting the whole paradigm by hand-copying
packfiles around?
-Tony
next reply other threads:[~2005-10-31 18:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-31 18:23 Luck, Tony [this message]
2005-10-31 18:44 ` git push sends more objects than it needs to Linus Torvalds
2005-10-31 19:36 ` Linus Torvalds
2005-10-31 19:50 ` Luck, Tony
2005-10-31 18:49 ` 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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20051031182355.GA7368@agluck-lia64.sc.intel.com \
--to=tony.luck@intel.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).