Skip to content

Commit

Permalink
manual: use 'URL' instead of 'url'.
Browse files Browse the repository at this point in the history
Just for consistency, use the spelling URL everywhere.

Signed-off-by: Lars Hjemli <hjemli@gmail.com>
Signed-off-by: Shawn O. Pearce <spearce@spearce.org>
  • Loading branch information
Ralf Wildenhues authored and Shawn O. Pearce committed Oct 16, 2007
1 parent b6cbca3 commit c901615
Showing 1 changed file with 4 additions and 4 deletions.
8 changes: 4 additions & 4 deletions Documentation/user-manual.txt
Original file line number Diff line number Diff line change
Expand Up @@ -1782,7 +1782,7 @@ $ git clone /path/to/repository
$ git pull /path/to/other/repository
-------------------------------------------------

or an ssh url:
or an ssh URL:

-------------------------------------------------
$ git clone ssh://yourhost/~you/repository
Expand Down Expand Up @@ -1843,7 +1843,7 @@ Exporting a git repository via the git protocol
This is the preferred method.

If someone else administers the server, they should tell you what
directory to put the repository in, and what git:// url it will appear
directory to put the repository in, and what git:// URL it will appear
at. You can then skip to the section
"<<pushing-changes-to-a-public-repository,Pushing changes to a public
repository>>", below.
Expand Down Expand Up @@ -1880,8 +1880,8 @@ $ chmod a+x hooks/post-update
gitlink:git-update-server-info[1], and the documentation
link:hooks.html[Hooks used by git].)

Advertise the url of proj.git. Anybody else should then be able to
clone or pull from that url, for example with a command line like:
Advertise the URL of proj.git. Anybody else should then be able to
clone or pull from that URL, for example with a command line like:

-------------------------------------------------
$ git clone http://yourserver.com/~you/proj.git
Expand Down

0 comments on commit c901615

Please sign in to comment.