git/Documentation/git-clone.txt, branch v2.5.2

clone: --dissociate option to mark that reference is only temporary

2014-10-15T21:34:45Z

While use of the --reference option to borrow objects from an existing local repository of the same project is an effective way to reduce traffic when cloning a project over the network, it makes the resulting "borrowing" repository dependent on the "borrowed" repository. After running git clone --reference=P $URL Q the resulting repository Q will be broken if the borrowed repository P disappears. The way to allow the borrowed repository to be removed is to repack the borrowing repository (i.e. run "git repack -a -d" in Q); while power users may know it very well, it is not easily discoverable. Teach a new "--dissociate" option to "git clone" to run this repacking for the user. Helped-by: Johannes Sixt Signed-off-by: Junio C Hamano

docs/git-clone: clarify use of --no-hardlinks option

2014-02-11T19:03:07Z

Current text claims optimization, implying the use of hardlinks, when this option ratchets down the level of efficiency. This change explains the difference made by using this option, namely copying instead of hardlinking, and why it may be useful. Signed-off-by: Albert L. Lash, IV Signed-off-by: Junio C Hamano

Merge branch 'ow/manpages-typofix'

2014-02-07T19:55:12Z

Various typofixes, all looked correct. * ow/manpages-typofix: Documentation: fix typos in man pages

Documentation: fix typos in man pages

2014-02-05T22:35:45Z

Signed-off-by: Øystein Walle Signed-off-by: Junio C Hamano

git-clone.txt: remove shallow clone limitations

2013-12-11T00:14:19Z

Now that git supports data transfer from or to a shallow clone, these limitations are not true anymore. Signed-off-by: Nguyễn Thái Ngọc Duy Signed-off-by: Junio C Hamano

Revert "git-clone.txt: remove the restriction on pushing from a shallow clone"

2013-07-15T15:35:32Z

This reverts commit dacd2bcc414e0b7aac36aaa400da0a743c4741cc. "It fails reliably without corrupting the receiving repository when it should fail" may be better than the situation before the receiving end was hardened recently, but the fact that sometimes the push does not go through still remains. It is better to advice the users that they cannot push from a shallow repository as a limitation before they decide to use (or not to use) a shallow clone. Signed-off-by: Junio C Hamano

git-clone.txt: remove the restriction on pushing from a shallow clone

2013-07-12T19:03:28Z

The document says one cannot push from a shallow clone. But that is not true (maybe it was at some point in the past). The client does not stop such a push nor does it give any indication to the receiver that this is a shallow push. If the receiver accepts it, it's in. Since 52fed6e (receive-pack: check connectivity before concluding "git push" - 2011-09-02), receive-pack is prepared to deal with broken push, a shallow push can't cause any corruption. Update the document to reflect that. Signed-off-by: Nguyễn Thái Ngọc Duy Signed-off-by: Junio C Hamano

Documentation: Update 'linux-2.6.git' -> 'linux.git'

2013-06-23T06:36:48Z

The 3.x tree has been out for a while now. The -2.6 repository name survived the initial release [1], but kernel.org now only lists 'linux.git' (for aegl as well as torvalds) [2]. [1]: http://article.gmane.org/gmane.linux.kernel/1147422 On 2011-05-30 01:47:57 GMT, Linus Torvalds wrote: > ... yes, that means that my git tree is still called > "linux-2.6.git" on kernel.org. [2]: http://git.kernel.org/cgit/ Signed-off-by: W. Trevor King Signed-off-by: Junio C Hamano

doc/clone: Pick more compelling paths for the --reference example

2013-06-23T06:35:00Z

There may be times when using one of your local repositories as a reference for a new clone make sense, but the implied version-bump in the old example isn't one of them. I think a more intuitive example is multi-user system with a central reference clone, and the new paths hint at this use case. Signed-off-by: W. Trevor King Signed-off-by: Junio C Hamano

doc/clone: Remove the '--bare -l -s' example

2013-06-23T06:34:54Z

There are other examples in git-clone.txt demonstrating both '--bare' and '-l -s'. Signed-off-by: W. Trevor King Signed-off-by: Junio C Hamano