From: "Ryan Moszynski" <ryan.m.public@gmail.com>
To: git@vger.kernel.org
Subject: git .pack expansion question
Date: Thu, 12 Jul 2007 15:03:01 -0400 [thread overview]
Message-ID: <5ed683f50707121203q52084b72o106616f1c8710141@mail.gmail.com> (raw)
hopefully this is the right list for this:
am i understanding this right?
if i run the command:
git-repack
this creates an .idx and a .pack file that together hold all the files
and other metadata for my git directory. What i can't figure out
though, is how to send just these two files to another machine over
the network, and then using only these two files, have git create a
replica of the original git directory that the .pack file was made
from. I've tried
mkdir git-test
cd git-test
cp pack-92fadfab20e56acbbf28ed45851d61dc0d35c6ab.idx && .pack ./
git-init-db
git add .
git-unpack-objects < pack-92fadfab20e56acbbf28ed45851d61dc0d35c6ab.pack
now, the objects that were created from my original files are in the
objects directory, but I need them expanded so my git directory is a
copy of the one i originally git-repack'ed. Is there an easy way to
do this? This is for back up and archival purposes.
here are three ways i know to do this already, none of which I like very much.
cloning a repository over a network,
drawback: git has to be installed on both machines
or
scp'ing my whole git directory over the network,
drawback: too many little files, scp is too slow
or
tar'ing up my git directory so i can send one file for everything,
drawback: since git already has a compression/expansion tool built in,
i shouldn't have to use another to be able to do what i need.
any comments appreciated,
ryan
next reply other threads:[~2007-07-12 19:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-12 19:03 Ryan Moszynski [this message]
2007-07-12 20:58 ` git .pack expansion question Brian Gernhardt
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=5ed683f50707121203q52084b72o106616f1c8710141@mail.gmail.com \
--to=ryan.m.public@gmail.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox