diff options
author | Michael J Gruber <git@drmicha.warpmail.net> | 2009-12-01 10:19:05 +0100 |
---|---|---|
committer | Junio C Hamano <gitster@pobox.com> | 2009-12-01 12:09:46 -0800 |
commit | 3c652d16713c27d0abb2003d83a237f7d47ef569 (patch) | |
tree | 86f567154d361532aa127a63da6cee20fc97426b /Documentation | |
parent | Documentation: Document --branch option in git clone synopsis (diff) | |
download | tgif-3c652d16713c27d0abb2003d83a237f7d47ef569.tar.xz |
Documentation: Fix a few i.e./e.g. mix-ups
A git bundle can be transported by several means (such as e-mail), not
only by snekaernet, so use e.g. instead of i.e.
The mix-up in git-bundle.txt is obvious.
Signed-off-by: Michael J Gruber <git@drmicha.warpmail.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'Documentation')
-rw-r--r-- | Documentation/git-bundle.txt | 2 | ||||
-rw-r--r-- | Documentation/gitcore-tutorial.txt | 2 |
2 files changed, 2 insertions, 2 deletions
diff --git a/Documentation/git-bundle.txt b/Documentation/git-bundle.txt index aee7e4a8c9..c3a066e60c 100644 --- a/Documentation/git-bundle.txt +++ b/Documentation/git-bundle.txt @@ -24,7 +24,7 @@ ssh, rsync, http) cannot be used. This command provides support for 'git-fetch' and 'git-pull' to operate by packaging objects and references in an archive at the originating machine, then importing those into another repository using 'git-fetch' and 'git-pull' -after moving the archive by some means (i.e., by sneakernet). As no +after moving the archive by some means (e.g., by sneakernet). As no direct connection between the repositories exists, the user must specify a basis for the bundle that is held by the destination repository: the bundle assumes that all objects in the basis are already in the diff --git a/Documentation/gitcore-tutorial.txt b/Documentation/gitcore-tutorial.txt index b3640c4e64..0382d2c0ad 100644 --- a/Documentation/gitcore-tutorial.txt +++ b/Documentation/gitcore-tutorial.txt @@ -602,7 +602,7 @@ $ git tag -s <tagname> ---------------- which will sign the current `HEAD` (but you can also give it another -argument that specifies the thing to tag, i.e., you could have tagged the +argument that specifies the thing to tag, e.g., you could have tagged the current `mybranch` point by using `git tag <tagname> mybranch`). You normally only do signed tags for major releases or things |