Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Browse files

Autogenerated HTML docs for v1.8.1.2-545-g2f19ad

  • Loading branch information...
commit 076ffcc834f02a4f11d7f4fe8825be3b065020ff 1 parent 3f2ed6f
@gitster authored
Showing with 2,181 additions and 2,106 deletions.
  1. +24 −0 RelNotes/1.8.2.txt
  2. +2 −2 blame-options.txt
  3. +1 −1  cmds-ancillaryinterrogators.txt
  4. +3 −3 cmds-foreignscminterface.txt
  5. +2 −2 cmds-mainporcelain.txt
  6. +2 −2 cmds-plumbinginterrogators.txt
  7. +1 −1  cmds-purehelpers.txt
  8. +1 −1  cmds-synchelpers.txt
  9. +2 −2 cmds-synchingrepositories.txt
  10. +56 −56 config.txt
  11. +1 −1  diff-config.txt
  12. +2 −2 diff-options.txt
  13. +7 −7 everyday.html
  14. +5 −5 everyday.txt
  15. +2 −2 git-annotate.html
  16. +3 −3 git-apply.html
  17. +2 −2 git-apply.txt
  18. +9 −9 git-archimport.html
  19. +8 −8 git-archimport.txt
  20. +2 −2 git-archive.html
  21. +1 −1  git-archive.txt
  22. +12 −12 git-bisect-lk2009.html
  23. +11 −11 git-bisect-lk2009.txt
  24. +3 −3 git-bisect.html
  25. +2 −2 git-bisect.txt
  26. +4 −4 git-blame.html
  27. +1 −1  git-blame.txt
  28. +2 −2 git-branch.html
  29. +1 −1  git-branch.txt
  30. +2 −2 git-bundle.html
  31. +1 −1  git-bundle.txt
  32. +3 −3 git-check-ref-format.html
  33. +2 −2 git-check-ref-format.txt
  34. +3 −3 git-checkout.html
  35. +2 −2 git-checkout.txt
  36. +5 −5 git-clean.html
  37. +4 −4 git-clean.txt
  38. +11 −11 git-clone.html
  39. +8 −8 git-clone.txt
  40. +6 −6 git-commit-tree.html
  41. +1 −1  git-commit-tree.txt
  42. +8 −8 git-commit.html
  43. +3 −3 git-commit.txt
  44. +61 −61 git-config.html
  45. +3 −3 git-credential-cache.html
  46. +2 −2 git-credential-cache.txt
  47. +4 −4 git-credential-store.html
  48. +3 −3 git-credential-store.txt
  49. +4 −4 git-credential.html
  50. +3 −3 git-credential.txt
  51. +4 −4 git-cvsexportcommit.html
  52. +3 −3 git-cvsexportcommit.txt
  53. +6 −6 git-cvsimport.html
  54. +5 −5 git-cvsimport.txt
  55. +15 −15 git-cvsserver.html
  56. +14 −14 git-cvsserver.txt
  57. +7 −7 git-daemon.html
  58. +6 −6 git-daemon.txt
  59. +2 −2 git-describe.html
  60. +1 −1  git-describe.txt
  61. +2 −2 git-diff-files.html
  62. +2 −2 git-diff-index.html
  63. +2 −2 git-diff-tree.html
  64. +4 −4 git-diff.html
  65. +1 −1  git-diff.txt
  66. +2 −2 git-difftool.html
  67. +1 −1  git-difftool.txt
  68. +5 −5 git-fetch.html
  69. +1 −1  git-fetch.txt
  70. +4 −4 git-filter-branch.html
  71. +3 −3 git-filter-branch.txt
  72. +8 −8 git-format-patch.html
  73. +5 −5 git-format-patch.txt
  74. +4 −4 git-fsck.html
  75. +3 −3 git-fsck.txt
  76. +2 −2 git-grep.html
  77. +1 −1  git-grep.txt
  78. +2 −2 git-gui.html
  79. +1 −1  git-gui.txt
  80. +2 −2 git-hash-object.html
  81. +1 −1  git-hash-object.txt
  82. +4 −4 git-help.html
  83. +3 −3 git-help.txt
  84. +2 −2 git-http-backend.html
  85. +1 −1  git-http-backend.txt
  86. +3 −3 git-http-fetch.html
  87. +2 −2 git-http-fetch.txt
  88. +4 −4 git-index-pack.html
  89. +3 −3 git-index-pack.txt
  90. +2 −2 git-init-db.html
  91. +1 −1  git-init-db.txt
  92. +9 −9 git-init.html
  93. +8 −8 git-init.txt
  94. +10 −10 git-log.html
  95. +1 −1  git-log.txt
  96. +2 −2 git-ls-files.html
  97. +1 −1  git-ls-files.txt
  98. +3 −3 git-merge-index.html
  99. +2 −2 git-merge-index.txt
  100. +7 −7 git-merge.html
  101. +2 −2 git-merge.txt
  102. +3 −3 git-mergetool--lib.html
  103. +2 −2 git-mergetool--lib.txt
  104. +3 −3 git-mktag.html
  105. +2 −2 git-mktag.txt
  106. +2 −2 git-mv.html
  107. +1 −1  git-mv.txt
  108. +43 −43 git-p4.html
  109. +42 −42 git-p4.txt
  110. +7 −7 git-pack-objects.html
  111. +6 −6 git-pack-objects.txt
  112. +8 −8 git-pull.html
  113. +4 −4 git-pull.txt
  114. +8 −8 git-push.html
  115. +4 −4 git-push.txt
  116. +3 −3 git-quiltimport.html
  117. +2 −2 git-quiltimport.txt
  118. +2 −2 git-rebase.html
  119. +1 −1  git-rebase.txt
  120. +2 −2 git-reflog.html
  121. +1 −1  git-reflog.txt
  122. +8 −8 git-remote-ext.html
  123. +7 −7 git-remote-ext.txt
  124. +5 −5 git-remote-fd.html
  125. +4 −4 git-remote-fd.txt
  126. +25 −25 git-remote-helpers.html
  127. +24 −24 git-remote-helpers.txt
  128. +2 −2 git-replace.html
  129. +1 −1  git-replace.txt
  130. +4 −4 git-rev-list.html
  131. +1 −1  git-rev-list.txt
  132. +8 −7 git-rev-parse.html
  133. +7 −5 git-rev-parse.txt
  134. +6 −6 git-rm.html
  135. +5 −5 git-rm.txt
  136. +2 −2 git-send-email.html
  137. +1 −1  git-send-email.txt
  138. +2 −2 git-send-pack.html
  139. +1 −1  git-send-pack.txt
  140. +3 −3 git-sh-setup.html
  141. +2 −2 git-sh-setup.txt
  142. +2 −2 git-show-index.html
  143. +1 −1  git-show-index.txt
  144. +4 −4 git-show.html
  145. +5 −5 git-status.html
  146. +4 −4 git-status.txt
  147. +2 −2 git-stripspace.html
  148. +1 −1  git-stripspace.txt
  149. +2 −2 git-submodule.html
  150. +1 −1  git-submodule.txt
  151. +45 −45 git-svn.html
  152. +44 −44 git-svn.txt
  153. +2 −2 git-tag.html
  154. +1 −1  git-tag.txt
  155. +24 −24 git-tools.html
  156. +22 −22 git-tools.txt
  157. +9 −9 git-update-index.html
  158. +8 −8 git-update-index.txt
  159. +2 −2 git-update-ref.html
  160. +1 −1  git-update-ref.txt
  161. +2 −2 git-upload-archive.html
  162. +1 −1  git-upload-archive.txt
  163. +2 −2 git-upload-pack.html
  164. +1 −1  git-upload-pack.txt
  165. +7 −7 git-var.html
  166. +6 −6 git-var.txt
  167. +3 −3 git-verify-pack.html
  168. +2 −2 git-verify-pack.txt
  169. +2 −2 git-verify-tag.html
  170. +1 −1  git-verify-tag.txt
  171. +3 −3 git-web--browse.html
  172. +2 −2 git-web--browse.txt
  173. +3 −3 git-whatchanged.html
  174. +2 −2 git-whatchanged.txt
  175. +57 −57 git.html
  176. +45 −45 git.txt
  177. +37 −37 gitattributes.html
  178. +36 −36 gitattributes.txt
  179. +8 −8 gitcli.html
  180. +7 −7 gitcli.txt
  181. +78 −78 gitcore-tutorial.html
  182. +77 −77 gitcore-tutorial.txt
  183. +13 −13 gitcredentials.html
  184. +12 −12 gitcredentials.txt
  185. +12 −12 gitcvs-migration.html
  186. +11 −11 gitcvs-migration.txt
  187. +2 −2 gitdiffcore.html
  188. +1 −1  gitdiffcore.txt
  189. +41 −32 gitglossary.html
  190. +2 −2 gitglossary.txt
  191. +5 −5 githooks.html
  192. +4 −4 githooks.txt
  193. +12 −12 gitignore.html
  194. +11 −11 gitignore.txt
  195. +5 −5 gitk.html
  196. +4 −4 gitk.txt
  197. +3 −3 gitmodules.html
  198. +2 −2 gitmodules.txt
  199. +2 −2 gitnamespaces.html
  200. +1 −1  gitnamespaces.txt
  201. +28 −10 gitrepository-layout.html
  202. +21 −9 gitrepository-layout.txt
  203. +3 −3 gitrevisions.html
  204. +1 −1  gitrevisions.txt
  205. +20 −20 gittutorial-2.html
  206. +19 −19 gittutorial-2.txt
  207. +24 −24 gittutorial.html
  208. +23 −23 gittutorial.txt
  209. +17 −17 gitweb.conf.html
  210. +16 −16 gitweb.conf.txt
  211. +12 −12 gitweb.html
  212. +11 −11 gitweb.txt
  213. +4 −4 gitworkflows.html
  214. +3 −3 gitworkflows.txt
  215. +33 −29 glossary-content.txt
  216. +8 −8 howto-index.html
  217. +6 −6 howto-index.txt
  218. +3 −3 howto/maintain-git.html
  219. +3 −3 howto/maintain-git.txt
  220. +10 −10 howto/new-command.html
  221. +10 −10 howto/new-command.txt
  222. +3 −3 howto/rebase-from-internal-branch.html
  223. +3 −3 howto/rebase-from-internal-branch.txt
  224. +4 −4 howto/rebuild-from-update-hook.html
  225. +4 −4 howto/rebuild-from-update-hook.txt
  226. +3 −3 howto/recover-corrupted-blob-object.html
  227. +2 −2 howto/recover-corrupted-blob-object.txt
  228. +2 −2 howto/revert-a-faulty-merge.html
  229. +1 −1  howto/revert-a-faulty-merge.txt
  230. +3 −3 howto/revert-branch-rebase.html
  231. +2 −2 howto/revert-branch-rebase.txt
  232. +10 −10 howto/setup-git-server-over-http.html
  233. +9 −9 howto/setup-git-server-over-http.txt
  234. +2 −2 howto/use-git-daemon.html
  235. +1 −1  howto/use-git-daemon.txt
  236. +3 −3 howto/using-signed-tag-in-pull-request.html
  237. +2 −2 howto/using-signed-tag-in-pull-request.txt
  238. +4 −4 i18n.txt
  239. +4 −4 merge-config.txt
  240. +2 −2 rev-list-options.txt
  241. +1 −1  revisions.txt
  242. +3 −3 technical/api-builtin.html
  243. +2 −2 technical/api-builtin.txt
  244. +6 −6 technical/api-config.html
  245. +5 −5 technical/api-config.txt
  246. +11 −11 technical/api-credentials.html
  247. +10 −10 technical/api-credentials.txt
  248. +2 −2 technical/api-directory-listing.html
  249. +1 −1  technical/api-directory-listing.txt
  250. +2 −2 technical/api-index-skel.txt
  251. +4 −4 technical/api-index.html
  252. +2 −2 technical/api-index.txt
  253. +2 −2 technical/api-parse-options.html
  254. +1 −1  technical/api-parse-options.txt
  255. +3 −3 technical/api-remote.html
  256. +2 −2 technical/api-remote.txt
  257. +6 −6 technical/index-format.html
  258. +4 −4 technical/index-format.txt
  259. +4 −4 technical/pack-format.html
  260. +2 −2 technical/pack-format.txt
  261. +11 −11 technical/pack-heuristics.html
  262. +10 −10 technical/pack-heuristics.txt
  263. +15 −15 technical/racy-git.html
  264. +13 −13 technical/racy-git.txt
  265. +1 −1  urls-remotes.txt
  266. +2 −2 urls.txt
  267. +140 −135 user-manual.html
  268. +108 −108 user-manual.txt
View
24 RelNotes/1.8.2.txt
@@ -33,6 +33,12 @@ UI, Workflows & Features
* Output from the tests is coloured using "green is okay, yellow is
questionable, red is bad and blue is informative" scheme.
+ * Mention of "GIT/Git/git" in the documentation have been updated to
+ be more uniform and consistent. The name of the system and the
+ concept it embodies is "Git"; the command the users type is "git".
+ All-caps "GIT" was merely a way to imitate "Git" typeset in small
+ caps in our ASCII text only documentation and to be avoided.
+
* In bare repositories, "git shortlog" and other commands now read
mailmap files from the tip of the history, to help running these
tools in server settings.
@@ -273,6 +279,10 @@ details).
try to use the textconv data incorrectly after it gets freed.
(merge be5c9fb jk/read-commit-buffer-data-after-free later to maint).
+ * We forgot to close the file descriptor reading from "gpg" output,
+ killing "git log --show-signature" on a long history.
+ (merge 7dac3f8 sb/gpg-plug-fd-leak later to maint).
+
* The way "git svn" asked for password using SSH_ASKPASS and
GIT_ASKPASS was not in line with the rest of the system.
@@ -285,6 +295,10 @@ details).
* "git pack-refs" that ran in parallel to another process that
created new refs had a nasty race.
+ * Rebasing the history of superproject with change in the submodule
+ has been broken since v1.7.12.
+ (merge e28efb1 jc/fake-ancestor-with-non-blobs later to maint).
+
* After "git add -N" and then writing a tree object out of the
index, the cache-tree data structure got corrupted.
@@ -303,6 +317,10 @@ details).
commit" does some time ago, but forgot to pay attention to the exit
status of the hook.
+ * A failure to push due to non-ff while on an unborn branch
+ dereferenced a NULL pointer when showing an error message.
+ (merge 1d2c14d ft/transport-report-segv later to maint).
+
* When users spell "cc:" in lowercase in the fake "header" in the
trailer part, "git send-email" failed to pick up the addresses from
there. As e-mail headers field names are case insensitive, this
@@ -342,6 +360,12 @@ details).
* When autoconf is used, any build on a different commit always ran
"config.status --recheck" even when unnecessary.
+ * A fix was added to the build procedure to work around buggy
+ versions of ccache broke the auto-generation of dependencies, which
+ unfortunately is still relevant because some people use ancient
+ distros.
+ (merge 6978934 jn/auto-depend-workaround-buggy-ccache later to maint).
+
* We have been carrying a translated and long-unmaintained copy of an
old version of the tutorial; removed.
View
4 blame-options.txt
@@ -95,7 +95,7 @@ of lines before or after the line given by <start>.
running extra passes of inspection.
+
<num> is optional but it is the lower bound on the number of
-alphanumeric characters that git must detect as moving/copying
+alphanumeric characters that Git must detect as moving/copying
within a file for it to associate those lines with the parent
commit. The default value is 20.
@@ -110,7 +110,7 @@ commit. The default value is 20.
looks for copies from other files in any commit.
+
<num> is optional but it is the lower bound on the number of
-alphanumeric characters that git must detect as moving/copying
+alphanumeric characters that Git must detect as moving/copying
between files for it to associate those lines with the parent
commit. And the default value is 40. If there are more than one
`-C` options given, the <num> argument of the last `-C` will
View
2  cmds-ancillaryinterrogators.txt
@@ -20,7 +20,7 @@ linkgit:git-get-tar-commit-id[1]::
Extract commit ID from an archive created using git-archive.
linkgit:git-help[1]::
- display help information about git.
+ Display help information about Git.
linkgit:git-instaweb[1]::
Instantly browse your working repository in gitweb.
View
6 cmds-foreignscminterface.txt
@@ -1,5 +1,5 @@
linkgit:git-archimport[1]::
- Import an Arch repository into git.
+ Import an Arch repository into Git.
linkgit:git-cvsexportcommit[1]::
Export a single commit to a CVS checkout.
@@ -8,7 +8,7 @@ linkgit:git-cvsimport[1]::
Salvage your data out of another SCM people love to hate.
linkgit:git-cvsserver[1]::
- A CVS server emulator for git.
+ A CVS server emulator for Git.
linkgit:git-imap-send[1]::
Send a collection of patches from stdin to an IMAP folder.
@@ -26,5 +26,5 @@ linkgit:git-send-email[1]::
Send a collection of patches as emails.
linkgit:git-svn[1]::
- Bidirectional operation between a Subversion repository and git.
+ Bidirectional operation between a Subversion repository and Git.
View
4 cmds-mainporcelain.txt
@@ -56,7 +56,7 @@ linkgit:git-gui[1]::
A portable graphical interface to Git.
linkgit:git-init[1]::
- Create an empty git repository or reinitialize an existing one.
+ Create an empty Git repository or reinitialize an existing one.
linkgit:git-log[1]::
Show commit logs.
@@ -107,5 +107,5 @@ linkgit:git-tag[1]::
Create, list, delete or verify a tag object signed with GPG.
linkgit:gitk[1]::
- The git repository browser.
+ The Git repository browser.
View
4 cmds-plumbinginterrogators.txt
@@ -47,8 +47,8 @@ linkgit:git-unpack-file[1]::
Creates a temporary file with a blob's contents.
linkgit:git-var[1]::
- Show a git logical variable.
+ Show a Git logical variable.
linkgit:git-verify-pack[1]::
- Validate packed git archive files.
+ Validate packed Git archive files.
View
2  cmds-purehelpers.txt
@@ -41,7 +41,7 @@ linkgit:git-sh-i18n[1]::
Git's i18n setup code for shell scripts.
linkgit:git-sh-setup[1]::
- Common git shell script setup code.
+ Common Git shell script setup code.
linkgit:git-stripspace[1]::
Remove unnecessary whitespace.
View
2  cmds-synchelpers.txt
@@ -1,5 +1,5 @@
linkgit:git-http-fetch[1]::
- Download from a remote git repository via HTTP.
+ Download from a remote Git repository via HTTP.
linkgit:git-http-push[1]::
Push objects over HTTP/DAV to another repository.
View
4 cmds-synchingrepositories.txt
@@ -1,5 +1,5 @@
linkgit:git-daemon[1]::
- A really simple server for git repositories.
+ A really simple server for Git repositories.
linkgit:git-fetch-pack[1]::
Receive missing objects from another repository.
@@ -8,7 +8,7 @@ linkgit:git-http-backend[1]::
Server side implementation of Git over HTTP.
linkgit:git-send-pack[1]::
- Push objects over git protocol to another repository.
+ Push objects over Git protocol to another repository.
linkgit:git-update-server-info[1]::
Update auxiliary info file to help dumb servers.
View
112 config.txt
@@ -1,14 +1,14 @@
CONFIGURATION FILE
------------------
-The git configuration file contains a number of variables that affect
-the git command's behavior. The `.git/config` file in each repository
+The Git configuration file contains a number of variables that affect
+the Git commands' behavior. The `.git/config` file in each repository
is used to store the configuration for that repository, and
`$HOME/.gitconfig` is used to store a per-user configuration as
fallback values for the `.git/config` file. The file `/etc/gitconfig`
can be used to store a system-wide default configuration.
-The configuration variables are used by both the git plumbing
+The configuration variables are used by both the Git plumbing
and the porcelains. The variables are divided into sections, wherein
the fully qualified variable name of the variable itself is the last
dot-separated segment and the section name is everything before the last
@@ -219,9 +219,9 @@ core.ignoreCygwinFSTricks::
core.ignorecase::
If true, this option enables various workarounds to enable
- git to work better on filesystems that are not case sensitive,
+ Git to work better on filesystems that are not case sensitive,
like FAT. For example, if a directory listing finds
- "makefile" when git expects "Makefile", git will assume
+ "makefile" when Git expects "Makefile", Git will assume
it is really the same file, and continue to remember it as
"Makefile".
+
@@ -230,13 +230,13 @@ will probe and set core.ignorecase true if appropriate when the repository
is created.
core.precomposeunicode::
- This option is only used by Mac OS implementation of git.
- When core.precomposeunicode=true, git reverts the unicode decomposition
+ This option is only used by Mac OS implementation of Git.
+ When core.precomposeunicode=true, Git reverts the unicode decomposition
of filenames done by Mac OS. This is useful when sharing a repository
between Mac OS and Linux or Windows.
- (Git for Windows 1.7.10 or higher is needed, or git under cygwin 1.7).
- When false, file names are handled fully transparent by git,
- which is backward compatible with older versions of git.
+ (Git for Windows 1.7.10 or higher is needed, or Git under cygwin 1.7).
+ When false, file names are handled fully transparent by Git,
+ which is backward compatible with older versions of Git.
core.trustctime::
If false, the ctime differences between the index and the
@@ -272,20 +272,20 @@ core.eol::
conversion.
core.safecrlf::
- If true, makes git check if converting `CRLF` is reversible when
+ If true, makes Git check if converting `CRLF` is reversible when
end-of-line conversion is active. Git will verify if a command
modifies a file in the work tree either directly or indirectly.
For example, committing a file followed by checking out the
same file should yield the original file in the work tree. If
this is not the case for the current setting of
- `core.autocrlf`, git will reject the file. The variable can
- be set to "warn", in which case git will only warn about an
+ `core.autocrlf`, Git will reject the file. The variable can
+ be set to "warn", in which case Git will only warn about an
irreversible conversion but continue the operation.
+
CRLF conversion bears a slight chance of corrupting data.
-When it is enabled, git will convert CRLF to LF during commit and LF to
+When it is enabled, Git will convert CRLF to LF during commit and LF to
CRLF during checkout. A file that contains a mixture of LF and
-CRLF before the commit cannot be recreated by git. For text
+CRLF before the commit cannot be recreated by Git. For text
files this is the right thing to do: it corrects line endings
such that we have only LF line endings in the repository.
But for binary files that are accidentally classified as text the
@@ -295,7 +295,7 @@ If you recognize such corruption early you can easily fix it by
setting the conversion type explicitly in .gitattributes. Right
after committing you still have the original file in your work
tree and this file is not yet corrupted. You can explicitly tell
-git that this file is binary and git will handle the file
+Git that this file is binary and Git will handle the file
appropriately.
+
Unfortunately, the desired effect of cleaning up text files with
@@ -340,7 +340,7 @@ is created.
core.gitProxy::
A "proxy command" to execute (as 'command host port') instead
of establishing direct connection to the remote server when
- using the git protocol for fetching. If the variable value is
+ using the Git protocol for fetching. If the variable value is
in the "COMMAND for DOMAIN" format, the command is applied only
on hostnames ending with the specified domain string. This variable
may be set multiple times and is matched in the given order;
@@ -399,7 +399,7 @@ Note that this variable is honored even when set in a configuration
file in a ".git" subdirectory of a directory and its value differs
from the latter directory (e.g. "/path/to/.git/config" has
core.worktree set to "/different/path"), which is most likely a
-misconfiguration. Running git commands in the "/path/to" directory will
+misconfiguration. Running Git commands in the "/path/to" directory will
still use "/different/path" as the root of the work tree and can cause
confusion unless you know what you are doing (e.g. you are creating a
read-only snapshot of the same index to a location different from the
@@ -431,7 +431,7 @@ core.sharedRepository::
several users in a group (making sure all the files and objects are
group-writable). When 'all' (or 'world' or 'everybody'), the
repository will be readable by all users, additionally to being
- group-shareable. When 'umask' (or 'false'), git will use permissions
+ group-shareable. When 'umask' (or 'false'), Git will use permissions
reported by umask(2). When '0xxx', where '0xxx' is an octal number,
files in the repository will have this mode value. '0xxx' will override
user's umask value (whereas the other options will only override
@@ -442,7 +442,7 @@ core.sharedRepository::
See linkgit:git-init[1]. False by default.
core.warnAmbiguousRefs::
- If true, git will warn you if the ref name you passed it is ambiguous
+ If true, Git will warn you if the ref name you passed it is ambiguous
and might match multiple refs in the .git/refs/ tree. True by default.
core.compression::
@@ -514,7 +514,7 @@ Common unit suffixes of 'k', 'm', or 'g' are supported.
core.excludesfile::
In addition to '.gitignore' (per-directory) and
- '.git/info/exclude', git looks into this file for patterns
+ '.git/info/exclude', Git looks into this file for patterns
of files which are not meant to be tracked. "`~/`" is expanded
to the value of `$HOME` and "`~user/`" to the specified user's
home directory. Its default value is $XDG_CONFIG_HOME/git/ignore.
@@ -532,7 +532,7 @@ core.askpass::
core.attributesfile::
In addition to '.gitattributes' (per-directory) and
- '.git/info/attributes', git looks into this file for attributes
+ '.git/info/attributes', Git looks into this file for attributes
(see linkgit:gitattributes[5]). Path expansions are made the same
way as for `core.excludesfile`. Its default value is
$XDG_CONFIG_HOME/git/attributes. If $XDG_CONFIG_HOME is either not
@@ -557,9 +557,9 @@ sequence.editor::
When not configured the default commit message editor is used instead.
core.pager::
- The command that git will use to paginate output. Can
+ The command that Git will use to paginate output. Can
be overridden with the `GIT_PAGER` environment
- variable. Note that git sets the `LESS` environment
+ variable. Note that Git sets the `LESS` environment
variable to `FRSX` if it is unset when it runs the
pager. One can change these settings by setting the
`LESS` variable to some other value. Alternately,
@@ -567,11 +567,11 @@ core.pager::
global basis by setting the `core.pager` option.
Setting `core.pager` has no effect on the `LESS`
environment variable behaviour above, so if you want
- to override git's default settings this way, you need
+ to override Git's default settings this way, you need
to be explicit. For example, to disable the S option
in a backward compatible manner, set `core.pager`
to `less -+S`. This will be passed to the shell by
- git, which will translate the final command to
+ Git, which will translate the final command to
`LESS=FRSX less -+S`.
core.whitespace::
@@ -600,7 +600,7 @@ core.whitespace::
does not trigger if the character before such a carriage-return
is not a whitespace (not enabled by default).
* `tabwidth=<n>` tells how many character positions a tab occupies; this
- is relevant for `indent-with-non-tab` and when git fixes `tab-in-indent`
+ is relevant for `indent-with-non-tab` and when Git fixes `tab-in-indent`
errors. The default tab width is 8. Allowed values are 1 to 63.
core.fsyncobjectfiles::
@@ -616,7 +616,7 @@ core.preloadindex::
+
This can speed up operations like 'git diff' and 'git status' especially
on filesystems like NFS that have weak caching semantics and thus
-relatively high IO latencies. With this set to 'true', git will do the
+relatively high IO latencies. With this set to 'true', Git will do the
index comparison to the filesystem data in parallel, allowing
overlapping IO's.
@@ -652,9 +652,9 @@ add.ignore-errors::
add.ignoreErrors::
Tells 'git add' to continue adding files when some files cannot be
added due to indexing errors. Equivalent to the '--ignore-errors'
- option of linkgit:git-add[1]. Older versions of git accept only
+ option of linkgit:git-add[1]. Older versions of Git accept only
`add.ignore-errors`, which does not follow the usual naming
- convention for configuration variables. Newer versions of git
+ convention for configuration variables. Newer versions of Git
honor `add.ignoreErrors` as well.
alias.*::
@@ -662,7 +662,7 @@ alias.*::
after defining "alias.last = cat-file commit HEAD", the invocation
"git last" is equivalent to "git cat-file commit HEAD". To avoid
confusion and troubles with script usage, aliases that
- hide existing git commands are ignored. Arguments are split by
+ hide existing Git commands are ignored. Arguments are split by
spaces, the usual shell quoting and escaping is supported.
quote pair and a backslash can be used to quote them.
+
@@ -709,7 +709,7 @@ branch.autosetupmerge::
branch.autosetuprebase::
When a new branch is created with 'git branch' or 'git checkout'
- that tracks another branch, this variable tells git to set
+ that tracks another branch, this variable tells Git to set
up pull to rebase instead of merge (see "branch.<name>.rebase").
When `never`, rebase is never automatically set to true.
When `local`, rebase is set to true for tracked branches of
@@ -890,7 +890,7 @@ color.status.<slot>::
one of `header` (the header text of the status message),
`added` or `updated` (files which are added but not committed),
`changed` (files which are changed but not added in the index),
- `untracked` (files which are not tracked by git),
+ `untracked` (files which are not tracked by Git),
`branch` (the current branch), or
`nobranch` (the color the 'no branch' warning is shown in, defaulting
to red). The values of these variables may be specified as in
@@ -904,7 +904,7 @@ color.ui::
to `always` if you want all output not intended for machine
consumption to use color, to `true` or `auto` if you want such
output to use color when written to the terminal, or to `false` or
- `never` if you prefer git commands not to use color unless enabled
+ `never` if you prefer Git commands not to use color unless enabled
explicitly with some other configuration or the `--color` option.
column.ui::
@@ -1021,7 +1021,7 @@ fetch.fsckObjects::
is used instead.
fetch.unpackLimit::
- If the number of objects fetched over the git native
+ If the number of objects fetched over the Git native
transfer is below this
limit, then the objects will be unpacked into loose object
files. However if the number of received objects equals or
@@ -1061,7 +1061,7 @@ format.subjectprefix::
format.signature::
The default for format-patch is to output a signature containing
- the git version number. Use this variable to change that default.
+ the Git version number. Use this variable to change that default.
Set this variable to the empty string ("") to suppress
signature generation.
@@ -1174,7 +1174,7 @@ gitcvs.logfile::
gitcvs.usecrlfattr::
If true, the server will look up the end-of-line conversion
attributes for files to determine the '-k' modes to use. If
- the attributes force git to treat a file as text,
+ the attributes force Git to treat a file as text,
the '-k' mode will be left blank so CVS clients will
treat it as text. If they suppress text conversion, the file
will be set with '-kb' mode, which suppresses any newline munging
@@ -1194,7 +1194,7 @@ gitcvs.allbinary::
gitcvs.dbname::
Database used by git-cvsserver to cache revision information
- derived from the git repository. The exact meaning depends on the
+ derived from the Git repository. The exact meaning depends on the
used database driver, for SQLite (which is the default driver) this
is a filename. Supports variable substitution (see
linkgit:git-cvsserver[1] for details). May not contain semicolons (`;`).
@@ -1406,7 +1406,7 @@ http.proxy::
http.cookiefile::
File containing previously stored cookie lines which should be used
- in the git http session, if they match the server. The file format
+ in the Git http session, if they match the server. The file format
of the file to read cookies from should be plain HTTP headers or
the Netscape/Mozilla cookie file format (see linkgit:curl[1]).
NOTE that the file specified with http.cookiefile is only used as
@@ -1428,7 +1428,7 @@ http.sslKey::
variable.
http.sslCertPasswordProtected::
- Enable git's password prompt for the SSL certificate. Otherwise
+ Enable Git's password prompt for the SSL certificate. Otherwise
OpenSSL will prompt the user, possibly many times, if the
certificate or private key is encrypted. Can be overridden by the
'GIT_SSL_CERT_PASSWORD_PROTECTED' environment variable.
@@ -1475,7 +1475,7 @@ http.noEPSV::
http.useragent::
The HTTP USER_AGENT string presented to an HTTP server. The default
- value represents the version of the client git such as git/1.7.1.
+ value represents the version of the client Git such as git/1.7.1.
This option allows you to override this value to a more common value
such as Mozilla/4.0. This may be necessary, for instance, if
connecting through a firewall that restricts HTTP connections to a set
@@ -1483,7 +1483,7 @@ http.useragent::
Can be overridden by the 'GIT_HTTP_USER_AGENT' environment variable.
i18n.commitEncoding::
- Character encoding the commit messages are stored in; git itself
+ Character encoding the commit messages are stored in; Git itself
does not care per se, but this information is necessary e.g. when
importing commits from emails or in the gitk graphical history
browser (and possibly at other places in the future or in other
@@ -1621,7 +1621,7 @@ mergetool.keepBackup::
`true` (i.e. keep the backup files).
mergetool.keepTemporaries::
- When invoking a custom merge tool, git uses a set of temporary
+ When invoking a custom merge tool, Git uses a set of temporary
files to pass to the tool. If the tool returns an error and this
variable is set to `true`, then these temporary files will be
preserved, otherwise they will be removed after the tool has
@@ -1649,7 +1649,7 @@ displayed.
notes.rewrite.<command>::
When rewriting commits with <command> (currently `amend` or
- `rebase`) and this variable is set to `true`, git
+ `rebase`) and this variable is set to `true`, Git
automatically copies your notes from the original to the
rewritten commit. Defaults to `true`, but see
"notes.rewriteRef" below.
@@ -1729,7 +1729,7 @@ pack.threads::
warning. This is meant to reduce packing time on multiprocessor
machines. The required amount of memory for the delta search window
is however multiplied by the number of threads.
- Specifying 0 will cause git to auto-detect the number of CPU's
+ Specifying 0 will cause Git to auto-detect the number of CPU's
and set the number of threads accordingly.
pack.indexVersion::
@@ -1741,11 +1741,11 @@ pack.indexVersion::
and this config option ignored whenever the corresponding pack is
larger than 2 GB.
+
-If you have an old git that does not understand the version 2 `*.idx` file,
+If you have an old Git that does not understand the version 2 `*.idx` file,
cloning or fetching over a non native protocol (e.g. "http" and "rsync")
that will copy both `*.pack` file and corresponding `*.idx` file from the
other side may give you a repository that cannot be accessed with your
-older version of git. If the `*.pack` file is smaller than 2 GB, however,
+older version of Git. If the `*.pack` file is smaller than 2 GB, however,
you can use linkgit:git-index-pack[1] on the *.pack file to regenerate
the `*.idx` file.
@@ -1760,7 +1760,7 @@ pack.packSizeLimit::
pager.<cmd>::
If the value is boolean, turns on or off pagination of the
- output of a particular git subcommand when writing to a tty.
+ output of a particular Git subcommand when writing to a tty.
Otherwise, turns on pagination for the subcommand using the
pager specified by the value of `pager.<cmd>`. If `--paginate`
or `--no-pager` is specified on the command line, it takes
@@ -1795,7 +1795,7 @@ pull.twohead::
The default merge strategy to use when pulling a single branch.
push.default::
- Defines the action git push should take if no refspec is given
+ Defines the action `git push` should take if no refspec is given
on the command line, no refspec is configured in the remote, and
no refspec is implied by any of the options given on the command
line. Possible values are:
@@ -1935,7 +1935,7 @@ remote.<name>.tagopt::
linkgit:git-fetch[1].
remote.<name>.vcs::
- Setting this to a value <vcs> will cause git to interact with
+ Setting this to a value <vcs> will cause Git to interact with
the remote with the git-remote-<vcs> helper.
remotes.<group>::
@@ -1945,9 +1945,9 @@ remotes.<group>::
repack.usedeltabaseoffset::
By default, linkgit:git-repack[1] creates packs that use
delta-base offset. If you need to share your repository with
- git older than version 1.4.4, either directly or via a dumb
+ Git older than version 1.4.4, either directly or via a dumb
protocol such as http, then you need to set this option to
- "false" and repack. Access from old git versions over the
+ "false" and repack. Access from old Git versions over the
native protocol are unaffected by this option.
rerere.autoupdate::
@@ -2016,7 +2016,7 @@ showbranch.default::
status.relativePaths::
By default, linkgit:git-status[1] shows paths relative to the
current directory. Setting this variable to `false` shows paths
- relative to the repository root (this was the default for git
+ relative to the repository root (this was the default for Git
prior to v1.5.4).
status.showUntrackedFiles::
@@ -2103,7 +2103,7 @@ url.<base>.insteadOf::
large number of repositories, and serves them with multiple
access methods, and some users need to use different access
methods, this feature allows people to specify any of the
- equivalent URLs and have git automatically rewrite the URL to
+ equivalent URLs and have Git automatically rewrite the URL to
the best alternative for the particular user, even for a
never-before-seen repository on the site. When more than one
insteadOf strings match a given URL, the longest match is used.
@@ -2114,11 +2114,11 @@ url.<base>.pushInsteadOf::
resulting URL will be pushed to. In cases where some site serves
a large number of repositories, and serves them with multiple
access methods, some of which do not allow push, this feature
- allows people to specify a pull-only URL and have git
+ allows people to specify a pull-only URL and have Git
automatically use an appropriate URL to push, even for a
never-before-seen repository on the site. When more than one
pushInsteadOf strings match a given URL, the longest match is
- used. If a remote has an explicit pushurl, git will ignore this
+ used. If a remote has an explicit pushurl, Git will ignore this
setting for that remote.
user.email::
View
2  diff-config.txt
@@ -99,7 +99,7 @@ diff.renameLimit::
detection; equivalent to the 'git diff' option '-l'.
diff.renames::
- Tells git to detect renames. If set to any boolean value, it
+ Tells Git to detect renames. If set to any boolean value, it
will enable basic rename detection. If set to "copies" or
"copy", it will detect copies, as well.
View
4 diff-options.txt
@@ -283,7 +283,7 @@ few lines that happen to match textually as the context, but as a
single deletion of everything old followed by a single insertion of
everything new, and the number `m` controls this aspect of the -B
option (defaults to 60%). `-B/70%` specifies that less than 30% of the
-original should remain in the result for git to consider it a total
+original should remain in the result for Git to consider it a total
rewrite (i.e. otherwise the resulting patch will be a series of
deletion and insertion mixed together with context lines).
+
@@ -307,7 +307,7 @@ ifdef::git-log[]
endif::git-log[]
If `n` is specified, it is a threshold on the similarity
index (i.e. amount of addition/deletions compared to the
- file's size). For example, `-M90%` means git should consider a
+ file's size). For example, `-M90%` means Git should consider a
delete/add pair to be a rename if more than 90% of the file
hasn't changed. Without a `%` sign, the number is to be read as
a fraction, with a decimal point before it. I.e., `-M5` becomes
View
14 everyday.html
@@ -4,7 +4,7 @@
<head>
<meta http-equiv="Content-Type" content="application/xhtml+xml; charset=UTF-8" />
<meta name="generator" content="AsciiDoc 8.6.8" />
-<title>Everyday GIT With 20 Commands Or So</title>
+<title>Everyday Git With 20 Commands Or So</title>
<style type="text/css">
/* Shared CSS for AsciiDoc xhtml11 and html5 backends */
@@ -731,7 +731,7 @@
</head>
<body class="article">
<div id="header">
-<h1>Everyday GIT With 20 Commands Or So</h1>
+<h1>Everyday Git With 20 Commands Or So</h1>
</div>
<div id="content">
<div id="preamble">
@@ -744,7 +744,7 @@
commands in addition to the above.</p></div>
<div class="paragraph"><p><a href="#Repository Administration">[Repository Administration]</a> commands are for system
administrators who are responsible for the care and feeding
-of git repositories.</p></div>
+of Git repositories.</p></div>
</div>
</div>
<div class="sect1">
@@ -878,7 +878,7 @@ <h3 id="_examples">Examples</h3>
</li>
<li>
<p>
-you need to tell git if you added a new file; removal and
+you need to tell Git if you added a new file; removal and
modification will be caught if you do <code>git commit -a</code> later.
</p>
</li>
@@ -1165,7 +1165,7 @@ <h2 id="_integrator_a_id_integrator_a">Integrator<a id="Integrator"></a></h2>
<h3 id="_examples_3">Examples</h3>
<div class="dlist"><dl>
<dt class="hdlist1">
-My typical GIT day.
+My typical Git day.
</dt>
<dd>
<div class="listingblock">
@@ -1338,7 +1338,7 @@ <h3 id="_examples_4">Examples</h3>
<div class="content">
<pre><code>$ cat /etc/xinetd.d/git-daemon
# default: off
-# description: The git server offers access to git repositories
+# description: The Git server offers access to Git repositories
service git
{
disable = no
@@ -1469,7 +1469,7 @@ <h3 id="_examples_4">Examples</h3>
<div id="footnotes"><hr /></div>
<div id="footer">
<div id="footer-text">
-Last updated 2012-05-02 15:00:44 PDT
+Last updated 2013-02-05 21:07:26 PST
</div>
</div>
</body>
View
10 everyday.txt
@@ -1,4 +1,4 @@
-Everyday GIT With 20 Commands Or So
+Everyday Git With 20 Commands Or So
===================================
<<Individual Developer (Standalone)>> commands are essential for
@@ -12,7 +12,7 @@ commands in addition to the above.
<<Repository Administration>> commands are for system
administrators who are responsible for the care and feeding
-of git repositories.
+of Git repositories.
Individual Developer (Standalone)[[Individual Developer (Standalone)]]
@@ -87,7 +87,7 @@ $ git log v2.43.. curses/ <12>
+
<1> create a new topic branch.
<2> revert your botched changes in `curses/ux_audio_oss.c`.
-<3> you need to tell git if you added a new file; removal and
+<3> you need to tell Git if you added a new file; removal and
modification will be caught if you do `git commit -a` later.
<4> to see what changes you are committing.
<5> commit everything as you have tested, with your sign-off.
@@ -229,7 +229,7 @@ commands in addition to the ones needed by participants.
Examples
~~~~~~~~
-My typical GIT day.::
+My typical Git day.::
+
------------
$ git status <1>
@@ -332,7 +332,7 @@ Run git-daemon to serve /pub/scm from xinetd.::
------------
$ cat /etc/xinetd.d/git-daemon
# default: off
-# description: The git server offers access to git repositories
+# description: The Git server offers access to Git repositories
service git
{
disable = no
View
4 git-annotate.html
@@ -944,7 +944,7 @@ <h2 id="_options">OPTIONS</h2>
running extra passes of inspection.
</p>
<div class="paragraph"><p>&lt;num&gt; is optional but it is the lower bound on the number of
-alphanumeric characters that git must detect as moving/copying
+alphanumeric characters that Git must detect as moving/copying
within a file for it to associate those lines with the parent
commit. The default value is 20.</p></div>
</dd>
@@ -963,7 +963,7 @@ <h2 id="_options">OPTIONS</h2>
looks for copies from other files in any commit.
</p>
<div class="paragraph"><p>&lt;num&gt; is optional but it is the lower bound on the number of
-alphanumeric characters that git must detect as moving/copying
+alphanumeric characters that Git must detect as moving/copying
between files for it to associate those lines with the parent
commit. And the default value is 40. If there are more than one
<code>-C</code> options given, the &lt;num&gt; argument of the last <code>-C</code> will
View
6 git-apply.html
@@ -765,7 +765,7 @@ <h2 id="_description">DESCRIPTION</h2>
With the <code>--index</code> option the patch is also applied to the index, and
with the <code>--cached</code> option the patch is only applied to the index.
Without these options, the command applies the patch only to files,
-and does not require them to be in a git repository.</p></div>
+and does not require them to be in a Git repository.</p></div>
<div class="paragraph"><p>This command applies the patch but does not create a commit. Use
<a href="git-am.html">git-am(1)</a> to create commits from patches generated by
<a href="git-format-patch.html">git-format-patch(1)</a> and/or received by email.</p></div>
@@ -1063,7 +1063,7 @@ <h2 id="_options">OPTIONS</h2>
<code>fix</code> outputs warnings for a few such errors, and applies the
patch after fixing them (<code>strip</code> is a synonym --- the tool
used to consider only trailing whitespace characters as errors, and the
- fix involved <em>stripping</em> them, but modern gits do more).
+ fix involved <em>stripping</em> them, but modern Gits do more).
</p>
</li>
<li>
@@ -1186,7 +1186,7 @@ <h2 id="_git">GIT</h2>
<div id="footnotes"><hr /></div>
<div id="footer">
<div id="footer-text">
-Last updated 2012-07-15 22:27:35 PDT
+Last updated 2013-02-05 21:07:26 PST
</div>
</div>
</body>
View
4 git-apply.txt
@@ -24,7 +24,7 @@ Reads the supplied diff output (i.e. "a patch") and applies it to files.
With the `--index` option the patch is also applied to the index, and
with the `--cached` option the patch is only applied to the index.
Without these options, the command applies the patch only to files,
-and does not require them to be in a git repository.
+and does not require them to be in a Git repository.
This command applies the patch but does not create a commit. Use
linkgit:git-am[1] to create commits from patches generated by
@@ -198,7 +198,7 @@ behavior:
* `fix` outputs warnings for a few such errors, and applies the
patch after fixing them (`strip` is a synonym --- the tool
used to consider only trailing whitespace characters as errors, and the
- fix involved 'stripping' them, but modern gits do more).
+ fix involved 'stripping' them, but modern Gits do more).
* `error` outputs warnings for a few such errors, and refuses
to apply the patch.
* `error-all` is similar to `error` but shows all errors.
View
18 git-archimport.html
@@ -737,7 +737,7 @@
<h2>NAME</h2>
<div class="sectionbody">
<p>git-archimport -
- Import an Arch repository into git
+ Import an Arch repository into Git
</p>
</div>
</div>
@@ -776,12 +776,12 @@ <h2 id="_description">DESCRIPTION</h2>
<em>git archimport</em> with the same parameters as the initial import to perform
incremental imports.</p></div>
<div class="paragraph"><p>While <em>git archimport</em> will try to create sensible branch names for the
-archives that it imports, it is also possible to specify git branch names
-manually. To do so, write a git branch name after each &lt;archive/branch&gt;
+archives that it imports, it is also possible to specify Git branch names
+manually. To do so, write a Git branch name after each &lt;archive/branch&gt;
parameter, separated by a colon. This way, you can shorten the Arch
-branch names and convert Arch jargon to git jargon, for example mapping a
+branch names and convert Arch jargon to Git jargon, for example mapping a
"PROJECT&#45;&#45;devo&#45;&#45;VERSION" branch to "master".</p></div>
-<div class="paragraph"><p>Associating multiple Arch branches to one git branch is possible; the
+<div class="paragraph"><p>Associating multiple Arch branches to one Git branch is possible; the
result will make the most sense only if no commits are made to the first
branch, after the second branch is created. Still, this is useful to
convert Arch repositories that had been rotated periodically.</p></div>
@@ -790,13 +790,13 @@ <h2 id="_description">DESCRIPTION</h2>
<div class="sect1">
<h2 id="_merges">MERGES</h2>
<div class="sectionbody">
-<div class="paragraph"><p>Patch merge data from Arch is used to mark merges in git as well. git
+<div class="paragraph"><p>Patch merge data from Arch is used to mark merges in Git as well. Git
does not care much about tracking patches, and only considers a merge when a
branch incorporates all the commits since the point they forked. The end result
-is that git will have a good idea of how far branches have diverged. So the
+is that Git will have a good idea of how far branches have diverged. So the
import process does lose some patch-trading metadata.</p></div>
<div class="paragraph"><p>Fortunately, when you try and merge branches imported from Arch,
-git will find a good merge base, and it has a good chance of identifying
+Git will find a good merge base, and it has a good chance of identifying
patches that have been traded out-of-sequence between the branches.</p></div>
</div>
</div>
@@ -900,7 +900,7 @@ <h2 id="_git">GIT</h2>
<div id="footnotes"><hr /></div>
<div id="footer">
<div id="footer-text">
-Last updated 2011-11-15 13:45:02 PST
+Last updated 2013-02-05 21:07:26 PST
</div>
</div>
</body>
View
16 git-archimport.txt
@@ -3,7 +3,7 @@ git-archimport(1)
NAME
----
-git-archimport - Import an Arch repository into git
+git-archimport - Import an Arch repository into Git
SYNOPSIS
@@ -40,13 +40,13 @@ directory. To follow the development of a project that uses Arch, rerun
incremental imports.
While 'git archimport' will try to create sensible branch names for the
-archives that it imports, it is also possible to specify git branch names
-manually. To do so, write a git branch name after each <archive/branch>
+archives that it imports, it is also possible to specify Git branch names
+manually. To do so, write a Git branch name after each <archive/branch>
parameter, separated by a colon. This way, you can shorten the Arch
-branch names and convert Arch jargon to git jargon, for example mapping a
+branch names and convert Arch jargon to Git jargon, for example mapping a
"PROJECT{litdd}devo{litdd}VERSION" branch to "master".
-Associating multiple Arch branches to one git branch is possible; the
+Associating multiple Arch branches to one Git branch is possible; the
result will make the most sense only if no commits are made to the first
branch, after the second branch is created. Still, this is useful to
convert Arch repositories that had been rotated periodically.
@@ -54,14 +54,14 @@ convert Arch repositories that had been rotated periodically.
MERGES
------
-Patch merge data from Arch is used to mark merges in git as well. git
+Patch merge data from Arch is used to mark merges in Git as well. Git
does not care much about tracking patches, and only considers a merge when a
branch incorporates all the commits since the point they forked. The end result
-is that git will have a good idea of how far branches have diverged. So the
+is that Git will have a good idea of how far branches have diverged. So the
import process does lose some patch-trading metadata.
Fortunately, when you try and merge branches imported from Arch,
-git will find a good merge base, and it has a good chance of identifying
+Git will find a good merge base, and it has a good chance of identifying
patches that have been traded out-of-sequence between the branches.
OPTIONS
View
4 git-archive.html
@@ -977,7 +977,7 @@ <h2 id="_attributes">ATTRIBUTES</h2>
</dt>
<dd>
<p>
- If the attribute export-subst is set for a file then git will
+ If the attribute export-subst is set for a file then Git will
expand several placeholders when adding this file to an archive.
See <a href="gitattributes.html">gitattributes(5)</a> for details.
</p>
@@ -1087,7 +1087,7 @@ <h2 id="_git">GIT</h2>
<div id="footnotes"><hr /></div>
<div id="footer">
<div id="footer-text">
-Last updated 2012-05-02 15:00:44 PDT
+Last updated 2013-02-05 21:07:26 PST
</div>
</div>
</body>
View
2  git-archive.txt
@@ -128,7 +128,7 @@ export-ignore::
added to archive files. See linkgit:gitattributes[5] for details.
export-subst::
- If the attribute export-subst is set for a file then git will
+ If the attribute export-subst is set for a file then Git will
expand several placeholders when adding this file to an archive.
See linkgit:gitattributes[5] for details.
View
24 git-bisect-lk2009.html
@@ -941,7 +941,7 @@ <h3 id="_starting_a_bisection">Starting a bisection</h3>
will be looking for the first commit that has a version like
"2.6.26-something", that is the commit that has a "SUBLEVEL = 26" line
in the top level Makefile. This is a toy example because there are
-better ways to find this commit with git than using "git bisect" (for
+better ways to find this commit with Git than using "git bisect" (for
example "git blame" or "git log -S&lt;string&gt;").</p></div>
</div>
<div class="sect2">
@@ -1148,7 +1148,7 @@ <h3 id="_bisection_algorithm">Bisection algorithm</h3>
<div class="paragraph"><p>So only the W and B commits will be kept. Because commits X and Y will
have been removed by rules a) and b) respectively, and because commits
G are removed by rule b) too.</p></div>
-<div class="paragraph"><p>Note for git users, that it is equivalent as keeping only the commit
+<div class="paragraph"><p>Note for Git users, that it is equivalent as keeping only the commit
given by:</p></div>
<div class="listingblock">
<div class="content">
@@ -1360,8 +1360,8 @@ <h3 id="_skip_algorithm_discussed">Skip algorithm discussed</h3>
<div class="paragraph"><p>After step 7) (in the skip algorithm), we could check if the second
commit has been skipped and return it if it is not the case. And in
fact that was the algorithm we used from when "git bisect skip" was
-developed in git version 1.5.4 (released on February 1st 2008) until
-git version 1.6.4 (released July 29th 2009).</p></div>
+developed in Git version 1.5.4 (released on February 1st 2008) until
+Git version 1.6.4 (released July 29th 2009).</p></div>
<div class="paragraph"><p>But Ingo Molnar and H. Peter Anvin (another well known linux kernel
developer) both complained that sometimes the best bisection points
all happened to be in an area where all the commits are
@@ -1640,10 +1640,10 @@ <h3 id="_adapting_your_work_flow">Adapting your work-flow</h3>
<div class="content">
<div class="paragraph"><p>To give some hard figures, we used to have an average report-to-fix
cycle of 142.6 hours (according to our somewhat weird bug-tracker
-which just measures wall-clock time). Since we moved to git, we&#8217;ve
+which just measures wall-clock time). Since we moved to Git, we&#8217;ve
lowered that to 16.2 hours. Primarily because we can stay on top of
the bug fixing now, and because everyone&#8217;s jockeying to get to fix
-bugs (we&#8217;re quite proud of how lazy we are to let git find the bugs
+bugs (we&#8217;re quite proud of how lazy we are to let Git find the bugs
for us). Each new release results in ~40% fewer bugs (almost certainly
due to how we now feel about writing tests).</p></div>
</div>
@@ -1816,9 +1816,9 @@ <h3 id="_git_replace">"git replace"</h3>
commits in already released history, for example to change the commit
message or the author. And it can also be used instead of git "grafts"
to link a repository with another old repository.</p></div>
-<div class="paragraph"><p>In fact it&#8217;s this last feature that "sold" it to the git community, so
-it is now in the "master" branch of git&#8217;s git repository and it should
-be released in git 1.6.5 in October or November 2009.</p></div>
+<div class="paragraph"><p>In fact it&#8217;s this last feature that "sold" it to the Git community, so
+it is now in the "master" branch of Git&#8217;s Git repository and it should
+be released in Git 1.6.5 in October or November 2009.</p></div>
<div class="paragraph"><p>One problem with "git replace" is that currently it stores all the
replacements refs in "refs/replace/", but it would be perhaps better
if the replacement refs that are useful only for bisecting would be in
@@ -1906,7 +1906,7 @@ <h2 id="_conclusion">Conclusion</h2>
<h2 id="_acknowledgements">Acknowledgements</h2>
<div class="sectionbody">
<div class="paragraph"><p>Many thanks to Junio Hamano for his help in reviewing this paper, for
-reviewing the patches I sent to the git mailing list, for discussing
+reviewing the patches I sent to the Git mailing list, for discussing
some ideas and helping me improve them, for improving "git bisect" a
lot and for his awesome work in maintaining and developing Git.</p></div>
<div class="paragraph"><p>Many thanks to Ingo Molnar for giving me very useful information that
@@ -1916,7 +1916,7 @@ <h2 id="_acknowledgements">Acknowledgements</h2>
<div class="paragraph"><p>Many thanks to Linus Torvalds for inventing, developing and
evangelizing "git bisect", Git and Linux.</p></div>
<div class="paragraph"><p>Many thanks to the many other great people who helped one way or
-another when I worked on git, especially to Andreas Ericsson, Johannes
+another when I worked on Git, especially to Andreas Ericsson, Johannes
Schindelin, H. Peter Anvin, Daniel Barkalow, Bill Lear, John Hawley,
Shawn O. Pierce, Jeff King, Sam Vilain, Jon Seymour.</p></div>
<div class="paragraph"><p>Many thanks to the Linux-Kongress program committee for choosing the
@@ -1979,7 +1979,7 @@ <h2 id="_references">References</h2>
<div id="footnotes"><hr /></div>
<div id="footer">
<div id="footer-text">
-Last updated 2012-11-20 13:06:02 PST
+Last updated 2013-02-05 21:07:26 PST
</div>
</div>
</body>
View
22 git-bisect-lk2009.txt
@@ -224,7 +224,7 @@ Note that the example that we will use is really a toy example, we
will be looking for the first commit that has a version like
"2.6.26-something", that is the commit that has a "SUBLEVEL = 26" line
in the top level Makefile. This is a toy example because there are
-better ways to find this commit with git than using "git bisect" (for
+better ways to find this commit with Git than using "git bisect" (for
example "git blame" or "git log -S<string>").
Driving a bisection manually
@@ -455,7 +455,7 @@ So only the W and B commits will be kept. Because commits X and Y will
have been removed by rules a) and b) respectively, and because commits
G are removed by rule b) too.
-Note for git users, that it is equivalent as keeping only the commit
+Note for Git users, that it is equivalent as keeping only the commit
given by:
-------------
@@ -710,8 +710,8 @@ Skip algorithm discussed
After step 7) (in the skip algorithm), we could check if the second
commit has been skipped and return it if it is not the case. And in
fact that was the algorithm we used from when "git bisect skip" was
-developed in git version 1.5.4 (released on February 1st 2008) until
-git version 1.6.4 (released July 29th 2009).
+developed in Git version 1.5.4 (released on February 1st 2008) until
+Git version 1.6.4 (released July 29th 2009).
But Ingo Molnar and H. Peter Anvin (another well known linux kernel
developer) both complained that sometimes the best bisection points
@@ -1025,10 +1025,10 @@ And here is what Andreas said about this work-flow <<5>>:
_____________
To give some hard figures, we used to have an average report-to-fix
cycle of 142.6 hours (according to our somewhat weird bug-tracker
-which just measures wall-clock time). Since we moved to git, we've
+which just measures wall-clock time). Since we moved to Git, we've
lowered that to 16.2 hours. Primarily because we can stay on top of
the bug fixing now, and because everyone's jockeying to get to fix
-bugs (we're quite proud of how lazy we are to let git find the bugs
+bugs (we're quite proud of how lazy we are to let Git find the bugs
for us). Each new release results in ~40% fewer bugs (almost certainly
due to how we now feel about writing tests).
_____________
@@ -1228,9 +1228,9 @@ commits in already released history, for example to change the commit
message or the author. And it can also be used instead of git "grafts"
to link a repository with another old repository.
-In fact it's this last feature that "sold" it to the git community, so
-it is now in the "master" branch of git's git repository and it should
-be released in git 1.6.5 in October or November 2009.
+In fact it's this last feature that "sold" it to the Git community, so
+it is now in the "master" branch of Git's Git repository and it should
+be released in Git 1.6.5 in October or November 2009.
One problem with "git replace" is that currently it stores all the
replacements refs in "refs/replace/", but it would be perhaps better
@@ -1324,7 +1324,7 @@ Acknowledgements
----------------
Many thanks to Junio Hamano for his help in reviewing this paper, for
-reviewing the patches I sent to the git mailing list, for discussing
+reviewing the patches I sent to the Git mailing list, for discussing
some ideas and helping me improve them, for improving "git bisect" a
lot and for his awesome work in maintaining and developing Git.
@@ -1337,7 +1337,7 @@ Many thanks to Linus Torvalds for inventing, developing and
evangelizing "git bisect", Git and Linux.
Many thanks to the many other great people who helped one way or
-another when I worked on git, especially to Andreas Ericsson, Johannes
+another when I worked on Git, especially to Andreas Ericsson, Johannes
Schindelin, H. Peter Anvin, Daniel Barkalow, Bill Lear, John Hawley,
Shawn O. Pierce, Jeff King, Sam Vilain, Jon Seymour.
View
6 git-bisect.html
@@ -890,13 +890,13 @@ <h3 id="_avoiding_testing_a_commit">Avoiding testing a commit</h3>
</div>
<div class="sect2">
<h3 id="_bisect_skip">Bisect skip</h3>
-<div class="paragraph"><p>Instead of choosing by yourself a nearby commit, you can ask git
+<div class="paragraph"><p>Instead of choosing by yourself a nearby commit, you can ask Git
to do it for you by issuing the command:</p></div>
<div class="listingblock">
<div class="content">
<pre><code>$ git bisect skip # Current version cannot be tested</code></pre>
</div></div>
-<div class="paragraph"><p>But git may eventually be unable to tell the first bad commit among
+<div class="paragraph"><p>But Git may eventually be unable to tell the first bad commit among
a bad commit and one or more skipped commits.</p></div>
<div class="paragraph"><p>You can even skip a range of commits, instead of just one commit,
using the "<em>&lt;commit1&gt;</em>..<em>&lt;commit2&gt;</em>" notation. For example:</p></div>
@@ -1121,7 +1121,7 @@ <h2 id="_git">GIT</h2>
<div id="footnotes"><hr /></div>
<div id="footer">
<div id="footer-text">
-Last updated 2011-11-15 13:45:02 PST
+Last updated 2013-02-05 21:07:26 PST
</div>
</div>
</body>
View
4 git-bisect.txt
@@ -169,14 +169,14 @@ the revision as good or bad in the usual manner.
Bisect skip
~~~~~~~~~~~~
-Instead of choosing by yourself a nearby commit, you can ask git
+Instead of choosing by yourself a nearby commit, you can ask Git
to do it for you by issuing the command:
------------
$ git bisect skip # Current version cannot be tested
------------
-But git may eventually be unable to tell the first bad commit among
+But Git may eventually be unable to tell the first bad commit among
a bad commit and one or more skipped commits.
You can even skip a range of commits, instead of just one commit,
View
8 git-blame.html
@@ -767,7 +767,7 @@ <h2 id="_description">DESCRIPTION</h2>
<div class="paragraph"><p>The report does not tell you anything about lines which have been deleted or
replaced; you need to use a tool such as <em>git diff</em> or the "pickaxe"
interface briefly mentioned in the following paragraph.</p></div>
-<div class="paragraph"><p>Apart from supporting file annotation, git also supports searching the
+<div class="paragraph"><p>Apart from supporting file annotation, Git also supports searching the
development history for when a code snippet occurred in a change. This makes it
possible to track when a code snippet was added to a file, moved or copied
between files, and eventually deleted or replaced. It works by searching for
@@ -962,7 +962,7 @@ <h2 id="_options">OPTIONS</h2>
running extra passes of inspection.
</p>
<div class="paragraph"><p>&lt;num&gt; is optional but it is the lower bound on the number of
-alphanumeric characters that git must detect as moving/copying
+alphanumeric characters that Git must detect as moving/copying
within a file for it to associate those lines with the parent
commit. The default value is 20.</p></div>
</dd>
@@ -981,7 +981,7 @@ <h2 id="_options">OPTIONS</h2>
looks for copies from other files in any commit.
</p>
<div class="paragraph"><p>&lt;num&gt; is optional but it is the lower bound on the number of
-alphanumeric characters that git must detect as moving/copying
+alphanumeric characters that Git must detect as moving/copying
between files for it to associate those lines with the parent
commit. And the default value is 40. If there are more than one
<code>-C</code> options given, the &lt;num&gt; argument of the last <code>-C</code> will
@@ -1364,7 +1364,7 @@ <h2 id="_git">GIT</h2>
<div id="footnotes"><hr /></div>
<div id="footer">
<div id="footer-text">
-Last updated 2012-10-01 13:59:22 PDT
+Last updated 2013-02-05 21:07:26 PST
</div>
</div>
</body>
View
2  git-blame.txt
@@ -30,7 +30,7 @@ The report does not tell you anything about lines which have been deleted or
replaced; you need to use a tool such as 'git diff' or the "pickaxe"
interface briefly mentioned in the following paragraph.
-Apart from supporting file annotation, git also supports searching the
+Apart from supporting file annotation, Git also supports searching the
development history for when a code snippet occurred in a change. This makes it
possible to track when a code snippet was added to a file, moved or copied
between files, and eventually deleted or replaced. It works by searching for
View
4 git-branch.html
@@ -782,7 +782,7 @@ <h2 id="_description">DESCRIPTION</h2>
<div class="paragraph"><p>Note that this will create the new branch, but it will not switch the
working tree to it; use "git checkout &lt;newbranch&gt;" to switch to the
new branch.</p></div>
-<div class="paragraph"><p>When a local branch is started off a remote-tracking branch, git sets up the
+<div class="paragraph"><p>When a local branch is started off a remote-tracking branch, Git sets up the
branch so that <em>git pull</em> will appropriately merge from
the remote-tracking branch. This behavior may be changed via the global
<code>branch.autosetupmerge</code> configuration flag. That setting can be
@@ -1232,7 +1232,7 @@ <h2 id="_git">GIT</h2>
<div id="footnotes"><hr /></div>
<div id="footer">
<div id="footer-text">
-Last updated 2012-09-25 12:07:50 PDT
+Last updated 2013-02-05 21:07:26 PST
</div>
</div>
</body>
View
2  git-branch.txt
@@ -45,7 +45,7 @@ Note that this will create the new branch, but it will not switch the
working tree to it; use "git checkout <newbranch>" to switch to the
new branch.
-When a local branch is started off a remote-tracking branch, git sets up the
+When a local branch is started off a remote-tracking branch, Git sets up the
branch so that 'git pull' will appropriately merge from
the remote-tracking branch. This behavior may be changed via the global
`branch.autosetupmerge` configuration flag. That setting can be
View
4 git-bundle.html
@@ -759,7 +759,7 @@ <h2 id="_description">DESCRIPTION</h2>
<div class="sectionbody">
<div class="paragraph"><p>Some workflows require that one or more branches of development on one
machine be replicated on another machine, but the two machines cannot
-be directly connected, and therefore the interactive git protocols (git,
+be directly connected, and therefore the interactive Git protocols (git,
ssh, rsync, http) cannot be used. This command provides support for
<em>git fetch</em> and <em>git pull</em> to operate by packaging objects and references
in an archive at the originating machine, then importing those into
@@ -971,7 +971,7 @@ <h2 id="_git">GIT</h2>
<div id="footnotes"><hr /></div>
<div id="footer">
<div id="footer-text">
-Last updated 2013-01-08 16:14:48 PST
+Last updated 2013-02-05 21:07:26 PST
</div>
</div>
</body>
View
2  git-bundle.txt
@@ -19,7 +19,7 @@ DESCRIPTION
Some workflows require that one or more branches of development on one
machine be replicated on another machine, but the two machines cannot
-be directly connected, and therefore the interactive git protocols (git,
+be directly connected, and therefore the interactive Git protocols (git,
ssh, rsync, http) cannot be used. This command provides support for
'git fetch' and 'git pull' to operate by packaging objects and references
in an archive at the originating machine, then importing those into
View
6 git-check-ref-format.html
@@ -759,13 +759,13 @@ <h2 id="_description">DESCRIPTION</h2>
<div class="sectionbody">
<div class="paragraph"><p>Checks if a given <em>refname</em> is acceptable, and exits with a non-zero
status if it is not.</p></div>
-<div class="paragraph"><p>A reference is used in git to specify branches and tags. A
+<div class="paragraph"><p>A reference is used in Git to specify branches and tags. A
branch head is stored in the <code>refs/heads</code> hierarchy, while
a tag is stored in the <code>refs/tags</code> hierarchy of the ref namespace
(typically in <code>$GIT_DIR/refs/heads</code> and <code>$GIT_DIR/refs/tags</code>
directories or, as entries in file <code>$GIT_DIR/packed-refs</code>
if refs are packed by <code>git gc</code>).</p></div>
-<div class="paragraph"><p>git imposes the following rules on how references are named:</p></div>
+<div class="paragraph"><p>Git imposes the following rules on how references are named:</p></div>
<div class="olist arabic"><ol class="arabic">
<li>
<p>
@@ -944,7 +944,7 @@ <h2 id="_git">GIT</h2>
<div id="footnotes"><hr /></div>
<div id="footer">
<div id="footer-text">
-Last updated 2012-05-02 15:00:44 PDT
+Last updated 2013-02-05 21:07:26 PST
</div>
</div>
</body>
View
4 git-check-ref-format.txt
@@ -18,14 +18,14 @@ DESCRIPTION
Checks if a given 'refname' is acceptable, and exits with a non-zero
status if it is not.
-A reference is used in git to specify branches and tags. A
+A reference is used in Git to specify branches and tags. A
branch head is stored in the `refs/heads` hierarchy, while
a tag is stored in the `refs/tags` hierarchy of the ref namespace
(typically in `$GIT_DIR/refs/heads` and `$GIT_DIR/refs/tags`
directories or, as entries in file `$GIT_DIR/packed-refs`
if refs are packed by `git gc`).
-git imposes the following rules on how references are named:
+Git imposes the following rules on how references are named:
. They can include slash `/` for hierarchical (directory)
grouping, but no slash-separated component can begin with a
View
6 git-checkout.html
@@ -1177,7 +1177,7 @@ <h2 id="_detached_head">DETACHED HEAD</h2>
|
tag 'v2.0' (refers to commit 'b')</code></pre>
</div></div>
-<div class="paragraph"><p>In fact, we can perform all the normal git operations. But, let&#8217;s look
+<div class="paragraph"><p>In fact, we can perform all the normal Git operations. But, let&#8217;s look
at what happens when we then checkout master:</p></div>
<div class="listingblock">
<div class="content">
@@ -1193,7 +1193,7 @@ <h2 id="_detached_head">DETACHED HEAD</h2>
</div></div>
<div class="paragraph"><p>It is important to realize that at this point nothing refers to commit
<em>f</em>. Eventually commit <em>f</em> (and by extension commit <em>e</em>) will be deleted
-by the routine git garbage collection process, unless we create a reference
+by the routine Git garbage collection process, unless we create a reference
before that happens. If we have not yet moved away from commit <em>f</em>,
any of these will create a reference to it:</p></div>
<div class="listingblock">
@@ -1349,7 +1349,7 @@ <h2 id="_git">GIT</h2>
<div id="footnotes"><hr /></div>
<div id="footer">
<div id="footer-text">
-Last updated 2012-12-21 15:43:33 PST
+Last updated 2013-02-05 21:07:26 PST
</div>
</div>
</body>
View
4 git-checkout.txt
@@ -333,7 +333,7 @@ a---b---c---d branch 'master' (refers to commit 'd')
tag 'v2.0' (refers to commit 'b')
------------
-In fact, we can perform all the normal git operations. But, let's look
+In fact, we can perform all the normal Git operations. But, let's look
at what happens when we then checkout master:
------------
@@ -350,7 +350,7 @@ a---b---c---d branch 'master' (refers to commit 'd')
It is important to realize that at this point nothing refers to commit
'f'. Eventually commit 'f' (and by extension commit 'e') will be deleted
-by the routine git garbage collection process, unless we create a reference
+by the routine Git garbage collection process, unless we create a reference
before that happens. If we have not yet moved away from commit 'f',
any of these will create a reference to it:
View
10 git-clean.html
@@ -756,7 +756,7 @@ <h2 id="_description">DESCRIPTION</h2>
<div class="sectionbody">
<div class="paragraph"><p>Cleans the working tree by recursively removing files that are not
under version control, starting from the current directory.</p></div>
-<div class="paragraph"><p>Normally, only files unknown to git are removed, but if the <em>-x</em>
+<div class="paragraph"><p>Normally, only files unknown to Git are removed, but if the <em>-x</em>
option is specified, ignored files are also removed. This can, for
example, be useful to remove all build products.</p></div>
<div class="paragraph"><p>If any optional <code>&lt;path&gt;...</code> arguments are given, only those paths
@@ -773,7 +773,7 @@ <h2 id="_options">OPTIONS</h2>
<dd>
<p>
Remove untracked directories in addition to untracked files.
- If an untracked directory is managed by a different git
+ If an untracked directory is managed by a different Git
repository, it is not removed by default. Use -f option twice
if you really want to remove such a directory.
</p>
@@ -786,7 +786,7 @@ <h2 id="_options">OPTIONS</h2>
</dt>
<dd>
<p>
- If the git configuration variable clean.requireForce is not set
+ If the Git configuration variable clean.requireForce is not set
to false, <em>git clean</em> will refuse to run unless given -f or -n.
</p>
</dd>
@@ -844,7 +844,7 @@ <h2 id="_options">OPTIONS</h2>
</dt>
<dd>
<p>
- Remove only files ignored by git. This may be useful to rebuild
+ Remove only files ignored by Git. This may be useful to rebuild
everything from scratch, but keep manually created files.
</p>
</dd>
@@ -867,7 +867,7 @@ <h2 id="_git">GIT</h2>
<div id="footnotes"><hr /></div>
<div id="footer">
<div id="footer-text">
-Last updated 2012-09-25 12:07:50 PDT
+Last updated 2013-02-05 21:07:26 PST
</div>
</div>
</body>
View
8 git-clean.txt
@@ -16,7 +16,7 @@ DESCRIPTION
Cleans the working tree by recursively removing files that are not
under version control, starting from the current directory.
-Normally, only files unknown to git are removed, but if the '-x'
+Normally, only files unknown to Git are removed, but if the '-x'
option is specified, ignored files are also removed. This can, for
example, be useful to remove all build products.
@@ -27,13 +27,13 @@ OPTIONS
-------
-d::
Remove untracked directories in addition to untracked files.
- If an untracked directory is managed by a different git
+ If an untracked directory is managed by a different Git
repository, it is not removed by default. Use -f option twice
if you really want to remove such a directory.
-f::
--force::
- If the git configuration variable clean.requireForce is not set
+ If the Git configuration variable clean.requireForce is not set
to false, 'git clean' will refuse to run unless given -f or -n.
-n::
@@ -60,7 +60,7 @@ OPTIONS
working directory to test a clean build.
-X::
- Remove only files ignored by git. This may be useful to rebuild
+ Remove only files ignored by Git. This may be useful to rebuild
everything from scratch, but keep manually created files.
SEE ALSO
View
22 git-clone.html
@@ -789,7 +789,7 @@ <h2 id="_options">OPTIONS</h2>
<dd>
<p>
When the repository to clone from is on a local machine,
- this flag bypasses the normal "git aware" transport
+ this flag bypasses the normal "Git aware" transport
mechanism and clones the repository by making a copy of
HEAD and everything under objects and refs directories.
The files under <code>.git/objects/</code> directory are hardlinked
@@ -800,10 +800,10 @@ <h2 id="_options">OPTIONS</h2>
repository is specified as a URL, then this flag is ignored (and we
never use the local optimizations). Specifying <code>--no-local</code> will
override the default when <code>/path/to/repo</code> is given, using the regular
-git transport instead.</p></div>
+Git transport instead.</p></div>
<div class="paragraph"><p>To force copying instead of hardlinking (which may be desirable if you
are trying to make a back-up of your repository), but still avoid the
-usual "git aware" transport mechanism, <code>--no-hardlinks</code> can be used.</p></div>
+usual "Git aware" transport mechanism, <code>--no-hardlinks</code> can be used.</p></div>
</dd>
<dt class="hdlist1">
--no-hardlinks
@@ -832,9 +832,9 @@ <h2 id="_options">OPTIONS</h2>
<div class="paragraph"><p><strong>NOTE</strong>: this is a possibly dangerous operation; do <strong>not</strong> use
it unless you understand what it does. If you clone your
repository using this option and then delete branches (or use any
-other git command that makes any existing commit unreferenced) in the
+other Git command that makes any existing commit unreferenced) in the
source repository, some objects may become unreferenced (or dangling).
-These objects may be removed by normal git operations (such as <code>git commit</code>)
+These objects may be removed by normal Git operations (such as <code>git commit</code>)
which automatically call <code>git gc --auto</code>. (See <a href="git-gc.html">git-gc(1)</a>.)
If these objects are removed and were referenced by the cloned repository,
then the cloned repository will become corrupt.</p></div>
@@ -913,7 +913,7 @@ <h2 id="_options">OPTIONS</h2>
</dt>
<dd>
<p>
- Make a <em>bare</em> GIT repository. That is, instead of
+ Make a <em>bare</em> Git repository. That is, instead of
creating <code>&lt;directory&gt;</code> and placing the administrative
files in <code>&lt;directory&gt;/.git</code>, make the <code>&lt;directory&gt;</code>
itself the <code>$GIT_DIR</code>. This obviously implies the <code>-n</code>
@@ -1061,8 +1061,8 @@ <h2 id="_options">OPTIONS</h2>
<p>
Instead of placing the cloned repository where it is supposed
to be, place the cloned repository at the specified directory,
- then make a filesytem-agnostic git symbolic link to there.
- The result is git repository can be separated from working
+ then make a filesytem-agnostic Git symbolic link to there.
+ The result is Git repository can be separated from working
tree.
</p>
</dd>
@@ -1156,7 +1156,7 @@ <h2 id="_git_urls_a_id_urls_a">GIT URLS<a id="URLS"></a></h2>
</p>
</li>
</ul></div>
-<div class="paragraph"><p>For local repositories, also supported by git natively, the following
+<div class="paragraph"><p>For local repositories, also supported by Git natively, the following
syntaxes may be used:</p></div>
<div class="ulist"><ul>
<li>
@@ -1172,7 +1172,7 @@ <h2 id="_git_urls_a_id_urls_a">GIT URLS<a id="URLS"></a></h2>
</ul></div>
<div class="paragraph"><p>These two syntaxes are mostly equivalent, except the former implies
--local option.</p></div>
-<div class="paragraph"><p>When git doesn&#8217;t know how to handle a certain transport protocol, it
+<div class="paragraph"><p>When Git doesn&#8217;t know how to handle a certain transport protocol, it
attempts to use the <em>remote-&lt;transport&gt;</em> remote helper, if one
exists. To explicitly request a remote helper, the following syntax
may be used:</p></div>
@@ -1292,7 +1292,7 @@ <h2 id="_git">GIT</h2>
<div id="footnotes"><hr /></div>
<div id="footer">
<div id="footer-text">
-Last updated 2012-11-13 14:31:09 PST
+Last updated 2013-02-05 21:07:26 PST
</div>
</div>
</body>
View
16 git-clone.txt
@@ -43,7 +43,7 @@ OPTIONS
--local::
-l::
When the repository to clone from is on a local machine,
- this flag bypasses the normal "git aware" transport
+ this flag bypasses the normal "Git aware" transport
mechanism and clones the repository by making a copy of
HEAD and everything under objects and refs directories.