summaryrefslogtreecommitdiffstats
path: root/gittutorial.txt
diff options
context:
space:
mode:
authorJunio C Hamano <junio@hera.kernel.org>2009-01-06 05:56:24 +0000
committerJunio C Hamano <junio@hera.kernel.org>2009-01-06 05:56:24 +0000
commit4fbdd440748fc26b29440ef85b9d60919a96fcb0 (patch)
tree4a2c9d11831441595005c13d866bb7340fa2723c /gittutorial.txt
parent10b7a34451b2849b893cd1002b8477307873ab30 (diff)
downloadgit-htmldocs-4fbdd440748fc26b29440ef85b9d60919a96fcb0.tar.gz
Autogenerated HTML docs for v1.6.1-48-ge9b8
Diffstat (limited to 'gittutorial.txt')
-rw-r--r--gittutorial.txt4
1 files changed, 2 insertions, 2 deletions
diff --git a/gittutorial.txt b/gittutorial.txt
index 7892244ef..458fafdb2 100644
--- a/gittutorial.txt
+++ b/gittutorial.txt
@@ -590,7 +590,7 @@ list. When the history has lines of development that diverged and
then merged back together, the order in which 'git-log' presents
those commits is meaningless.
-Most projects with multiple contributors (such as the linux kernel,
+Most projects with multiple contributors (such as the Linux kernel,
or git itself) have frequent merges, and 'gitk' does a better job of
visualizing their history. For example,
@@ -642,7 +642,7 @@ digressions that may be interesting at this point are:
* linkgit:git-format-patch[1], linkgit:git-am[1]: These convert
series of git commits into emailed patches, and vice versa,
- useful for projects such as the linux kernel which rely heavily
+ useful for projects such as the Linux kernel which rely heavily
on emailed patches.
* linkgit:git-bisect[1]: When there is a regression in your