From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: James Pickens <jepicken@gmail.com>, Git ML <git@vger.kernel.org>
Subject: Re: 'git clone' doesn't use alternates automatically?
Date: Sat, 31 Jan 2009 17:19:31 -0800 [thread overview]
Message-ID: <7v7i4b2bto.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <20090131215514.GB9415@coredump.intra.peff.net> (Jeff King's message of "Sat, 31 Jan 2009 16:55:14 -0500")
Jeff King <peff@peff.net> writes:
> - without either, copy alternates from origin, but _don't_ use
> alternates while cloning
Are you talking about a local clone optimization that does hardlink from
the source repository?
I am fairly certain that copying alternates from the source repository was
not an intended behaviour but was a consequence of lazy coding of how we
copy (or link) everything from it. The original was literally the simple
matter of:
find objects ! -type d -print | cpio $cpio_quiet_flag -pumd$l "$GIT_DIR/"
whose intention was to copy objects/?? and objects/pack/. and it wasn't
even part of the design consideration to worry about what would happen to
the alternates the source repository might have in objects/info/.
next prev parent reply other threads:[~2009-02-01 1:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-30 22:12 'git clone' doesn't use alternates automatically? James Pickens
2009-01-31 7:12 ` Jeff King
2009-01-31 20:08 ` James Pickens
2009-01-31 21:08 ` Jakub Narebski
2009-01-31 21:43 ` James Pickens
2009-01-31 21:55 ` Jeff King
2009-02-01 1:19 ` Junio C Hamano [this message]
2009-02-02 13:07 ` Jeff King
2009-02-03 4:30 ` Junio C Hamano
2009-02-03 6:06 ` Jeff King
2009-02-01 0:55 ` Junio C Hamano
2009-02-01 1:32 ` James Pickens
2009-02-01 1:38 ` 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=7v7i4b2bto.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=jepicken@gmail.com \
--cc=peff@peff.net \
/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;
as well as URLs for NNTP newsgroup(s).