From: Brandon Casey <casey@nrlssc.navy.mil>
To: git@vger.kernel.org
Subject: clarify git clone --local --shared --reference
Date: Mon, 04 Jun 2007 18:53:34 -0500 [thread overview]
Message-ID: <4664A5FE.30208@nrlssc.navy.mil> (raw)
I think the goal of these three objects is space savings (and speed),
but I don't understand when I should prefer one option over another, or
when/whether to use a combination of them. And I am unsure (SCARED)
about any side effects they may have.
This is all based on the information in git-clone.txt. If there is more
detail someplace else please let me know.
1) What does local mean?
--local says repository must be on the "local" machine and claims it
attempts to make hardlinks when possible. Of course hard links cannot
be created across filesystems, so are there other speedups/space
savings when repository is on local machine but not on the same
filesystem? Is this option still valid then?
2) Does --shared imply shared write access? Does --local?
I'll point out that git-init has an option with the same name.
3) --shared seems like a special case of --reference? Are there
differences?
4) what happens if the source repository dissappears? Is --local ok
but --shared screwed?
4) is space savings obtained only at initial clone? or is it on going?
does a future git pull from the source repository create new hard
links where possible?
Can --shared be used with --reference. Can --reference be used multiple
times (and would I want to). Does -l with -s get you anything? (the
examples use this)
thanks,
-brandon
next reply other threads:[~2007-06-05 0:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-04 23:53 Brandon Casey [this message]
2007-06-05 4:50 ` clarify git clone --local --shared --reference Shawn O. Pearce
2007-06-05 16:30 ` Brandon Casey
2007-06-06 5:11 ` Shawn O. Pearce
2007-06-06 18:50 ` Brandon Casey
2007-06-06 18:55 ` Brandon Casey
2007-06-08 5:37 ` Shawn O. Pearce
2007-06-08 15:57 ` Loeliger Jon-LOELIGER
2007-06-08 18:35 ` Brandon Casey
2007-06-13 23:07 ` Brandon Casey
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=4664A5FE.30208@nrlssc.navy.mil \
--to=casey@nrlssc.navy.mil \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.