aboutsummaryrefslogtreecommitdiff
path: root/Documentation
diff options
context:
space:
mode:
authorJim Meyering <jim@meyering.net>2007-03-18 18:39:56 +0100
committerJ. Bruce Fields <bfields@citi.umich.edu>2007-03-18 21:53:29 -0400
commit21f13ee203b0dfe5bd9fdd18897cc11343f09ef7 (patch)
treebb6005ab2bb46c68ffc1f59ab255e1f8e4269b9b /Documentation
parent0a3985dcfbab7359e5b5e198061d03df56c4055c (diff)
downloadgit-21f13ee203b0dfe5bd9fdd18897cc11343f09ef7.tar.gz
git-21f13ee203b0dfe5bd9fdd18897cc11343f09ef7.tar.xz
user-manual.txt: fix a tiny typo.
"file patch" was doubtless intended to be "file path", but "directory name" is clearer. Signed-off-by: Jim Meyering <jim@meyering.net> Signed-off-by: "J. Bruce Fields" <bfields@citi.umich.edu>
Diffstat (limited to 'Documentation')
-rw-r--r--Documentation/user-manual.txt2
1 files changed, 1 insertions, 1 deletions
diff --git a/Documentation/user-manual.txt b/Documentation/user-manual.txt
index 0919574fb..773f65ef8 100644
--- a/Documentation/user-manual.txt
+++ b/Documentation/user-manual.txt
@@ -1698,7 +1698,7 @@ If you and maintainer both have accounts on the same machine, then
then you can just pull changes from each other's repositories
directly; note that all of the commands (gitlink:git-clone[1],
git-fetch[1], git-pull[1], etc.) that accept a URL as an argument
-will also accept a local file patch; so, for example, you can
+will also accept a local directory name; so, for example, you can
use
-------------------------------------------------