From: "Luck, Tony" <tony.luck@intel.com>
To: Linus Torvalds <torvalds@osdl.org>
Cc: git@vger.kernel.org
Subject: Re: git push sends more objects than it needs to
Date: Mon, 31 Oct 2005 11:50:48 -0800 [thread overview]
Message-ID: <20051031195048.GA9231@agluck-lia64.sc.intel.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0510311119170.27915@g5.osdl.org>
On Mon, Oct 31, 2005 at 11:36:09AM -0800, Linus Torvalds wrote:
> a) The "don't do that then" approach:
>
> Don't go behind git's back and add objects on your own, and expect git
> to realize what you did. ;^p
To be a responsible kernel.org git user I need to use packfiles. The
cheapest and easiest way to do that is to steal them from you.
> b) The "live with it" approach:
>
> You copied the pack by hand, and that will keep git-unpack-objects
> from duplicating the objects, but you'll still waste time and network
> when trying pushing the objects (just once, though).
>
> Ie this is what happened this time: nothing really lost, and the end
> result is fine. Now you know why it happened, and you're fine.
I like this one best. There's a pretty fat pipe between here and
kernel.org ... more of the time wasted appeared to be on the
unpacking part than on the transfer.
> d) Just let git do it for you.
>
> Copy the pack-files, or add my object directory as an "alternates" for
> your object directory, do the "git prune-objects", and then _locally_
> on master.kernel.org just do something like
Longer term (when everyone is pulling using the "git" protocol)
adding your object directory to my info/alternates looks to be
the best thing.
-Tony
next prev parent reply other threads:[~2005-10-31 19:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-31 18:23 git push sends more objects than it needs to Luck, Tony
2005-10-31 18:44 ` Linus Torvalds
2005-10-31 19:36 ` Linus Torvalds
2005-10-31 19:50 ` Luck, Tony [this message]
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=20051031195048.GA9231@agluck-lia64.sc.intel.com \
--to=tony.luck@intel.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.
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).