Re: [PATCH] Documentation: Note about the meaning of "clone"

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



El 15/6/2008, a las 15:05, Robin Rosenberg escribió:

Clarify that a clone is not an exact copy.

Signed-off-by: Robin Rosenberg <robin.rosenberg@xxxxxxxxxx>
---
Documentation/git-clone.txt |    7 ++++++-
1 files changed, 6 insertions(+), 1 deletions(-)

diff --git a/Documentation/git-clone.txt b/Documentation/git-clone.txt
index 7973e6a..c9bc627 100644
--- a/Documentation/git-clone.txt
+++ b/Documentation/git-clone.txt
@@ -31,7 +31,12 @@ This default configuration is achieved by creating references to
the remote branch heads under `$GIT_DIR/refs/remotes/origin` and
by initializing `remote.origin.url` and `remote.origin.fetch`
configuration variables.
-
++
+*NOTE*: Although this command is called clone, the clone is not identical
+in all respects. Local branches in the repository being cloned
+becomes remote tracking branches in the clone and remote tracking

Grammar: "become", not "becomes"


+branches are not cloned at all. For security reasone the config sections
+and triggers are not cloned either.

Typo: "security reasons", not "security reasone"

You might also want to mention that the clone is not necessarily a redundant _copy_ of the original repo, because at least for local clones on the same file system clone will use hard links rather than actually making a copy, unless you explicitly tell it not to.

W

--
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

[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]

  Powered by Linux