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
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
