@matheusbsbs / matheus-bagliano / commits / c90161586c
Fork 0

manual: use 'URL' instead of 'url'.

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>

Ralf Wildenhues committed Oct 9, 2007 at 23:03 UTC c90161586c174f740950ed56a748702ea3d9d6a1
1 file changed +4 -4
Documentation/user-manual.txt
+4 -4
@@ -1782,7 +1782,7 @@ $ git clone /path/to/repository
1782 $ git pull /path/to/other/repository
1783 -------------------------------------------------
1784
1785 -or an ssh url:
1785 +or an ssh URL:
1786
1787 -------------------------------------------------
1788 $ git clone ssh://yourhost/~you/repository
@@ -1843,7 +1843,7 @@ Exporting a git repository via the git protocol
1843 This is the preferred method.
1844
1845 If someone else administers the server, they should tell you what
1846 -directory to put the repository in, and what git:// url it will appear
1846 +directory to put the repository in, and what git:// URL it will appear
1847 at. You can then skip to the section
1848 "<<pushing-changes-to-a-public-repository,Pushing changes to a public
1849 repository>>", below.
@@ -1880,8 +1880,8 @@ $ chmod a+x hooks/post-update
1880 gitlink:git-update-server-info[1], and the documentation
1881 link:hooks.html[Hooks used by git].)
1882
1883 -Advertise the url of proj.git. Anybody else should then be able to
1884 -clone or pull from that url, for example with a command line like:
1883 +Advertise the URL of proj.git. Anybody else should then be able to
1884 +clone or pull from that URL, for example with a command line like:
1885
1886 -------------------------------------------------
1887 $ git clone http://yourserver.com/~you/proj.git