path: root/Documentation
diff options
authorJunio C Hamano <>2013-02-11 04:40:44 (GMT)
committerJunio C Hamano <>2013-02-11 04:40:44 (GMT)
commite1ebf212377837d676b0b28a821c022b0a3e57f3 (patch)
treebd04c38ccbd6bd559f5cb007bc84a592df4191a5 /Documentation
parent271cd23527c851ec5dd31a8603a8b25f936eb9e1 (diff)
parent901fd180c9d19025bafefc34e131125628169bdd (diff)
Merge branch 'maint'
* maint: user-manual: Rewrite git-gc section for automatic packing user-manual: Fix 'you - Git' -> 'you--Git' typo user-manual: Fix 'http' -> 'HTTP' typos user-manual: Fix 'both: so' -> 'both; so' typo
Diffstat (limited to 'Documentation')
1 files changed, 10 insertions, 16 deletions
diff --git a/Documentation/user-manual.txt b/Documentation/user-manual.txt
index 5077e7c..32cadc3 100644
--- a/Documentation/user-manual.txt
+++ b/Documentation/user-manual.txt
@@ -782,7 +782,7 @@ e05db0fd4f31dde7005f075a84f96b360d05984b
Or you could recall that the ... operator selects all commits
contained reachable from either one reference or the other but not
-both: so
+both; so
$ git log origin...master
@@ -1562,17 +1562,11 @@ Ensuring good performance
On large repositories, Git depends on compression to keep the history
-information from taking up too much space on disk or in memory.
-This compression is not performed automatically. Therefore you
-should occasionally run linkgit:git-gc[1]:
-$ git gc
-to recompress the archive. This can be very time-consuming, so
-you may prefer to run `git gc` when you are not doing other work.
+information from taking up too much space on disk or in memory. Some
+Git commands may automatically run linkgit:git-gc[1], so you don't
+have to worry about running it manually. However, compressing a large
+repository may take a while, so you may want to call `gc` explicitly
+to avoid automatic compression kicking in when it is not convenient.
@@ -1931,11 +1925,11 @@ linkgit:git-daemon[1] man page for details. (See especially the
examples section.)
-Exporting a Git repository via http
+Exporting a git repository via HTTP
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
a directory that is exported by the web server, and make some
@@ -1961,7 +1955,7 @@ $ git clone
(See 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
@@ -3396,7 +3390,7 @@ $ git log --raw --all
and just looked for the sha of the missing object (4b9458b..) in that
-whole thing. It's up to you - Git does *have* a lot of information, it is
+whole thing. It's up to you--Git does *have* a lot of information, it is
just missing one particular blob version.