From: Junio C Hamano <junkio@cox.net>
To: Tony Luck <tony.luck@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: time to update with new packs
Date: Sat, 01 Oct 2005 00:18:59 -0700 [thread overview]
Message-ID: <7vacht902k.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: 12c511ca0509302140o4263020bsc337594609175173@mail.gmail.com
Tony Luck <tony.luck@gmail.com> writes:
> 1) Link the new pack files from Linus' objects/pack directory
> to my objects/pack directory.
>
> 2) $ GIT_DIR=. git prune-packed # in my directory
>
> 3) $ GIT_DIR=. git update-server-info # ditto
When everybody uses more recent clients, you could say
"/pub/scm/.../torvalds/linux-2.6.git/objects" in your
objects/info/alternates file and not worry about step (1). git
native transport has known about the alternate mechanism since
the inception. The alternate mechanism support in "git fetch"
and "git clone" for rsync and http transports is a relatively
recent addition (appeared just before 0.99.7).
So (1) is not necessary for git native transport once you have
"alternate" file, but for other transports (1) is probably still
helpful at this point.
Also, enabling hooks/post-update in your public repository would
save you from worrying about (3), provided if the only way you
update it is by pushing into it, which I think is what usually
people are doing.
prev parent reply other threads:[~2005-10-01 7:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-01 4:40 time to update with new packs Tony Luck
2005-10-01 7:18 ` Junio C Hamano [this message]
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=7vacht902k.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=tony.luck@gmail.com \
/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