user-manual: Fix 'http' -> 'HTTP' typos

HTTP is an acronym which has not (yet) made the transition to word
status (unlike "laser", probably because lasers are inherently cooler
than HTTP ;).

Signed-off-by: W. Trevor King <wking@tremily.us>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
This commit is contained in:
W. Trevor King
2013-02-10 10:10:37 -05:00
committed by Junio C Hamano
parent ddd2369c5c
commit de3f2c7b46

View File

@ -1931,11 +1931,11 @@ linkgit:git-daemon[1] man page for details. (See especially the
examples section.) examples section.)
[[exporting-via-http]] [[exporting-via-http]]
Exporting a git repository via http Exporting a git repository via HTTP
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
The git protocol gives better performance and reliability, but on a The git protocol gives better performance and reliability, but on a
host with a web server set up, http exports may be simpler to set up. host with a web server set up, HTTP exports may be simpler to set up.
All you need to do is place the newly created bare git repository in All you need to do is place the newly created bare git repository in
a directory that is exported by the web server, and make some a directory that is exported by the web server, and make some
@ -1961,7 +1961,7 @@ $ git clone http://yourserver.com/~you/proj.git
(See also (See also
link:howto/setup-git-server-over-http.txt[setup-git-server-over-http] link:howto/setup-git-server-over-http.txt[setup-git-server-over-http]
for a slightly more sophisticated setup using WebDAV which also for a slightly more sophisticated setup using WebDAV which also
allows pushing over http.) allows pushing over HTTP.)
[[pushing-changes-to-a-public-repository]] [[pushing-changes-to-a-public-repository]]
Pushing changes to a public repository Pushing changes to a public repository