Andrew's git
/
gitweb.git
/ diff
summary
|
log
|
commit
| diff |
tree
commit
grep
author
committer
pickaxe
?
re
Fix spelling mistakes in user manual
author
Shawn Bohrer
<shawn.bohrer@gmail.com>
Thu, 13 Dec 2007 04:36:21 +0000
(22:36 -0600)
committer
Junio C Hamano
<gitster@pobox.com>
Thu, 13 Dec 2007 17:46:52 +0000
(09:46 -0800)
Signed-off-by: Shawn Bohrer <shawn.bohrer@gmail.com>
Acked-by: J. Bruce Fields <bfields@citi.umich.edu>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Documentation/user-manual.txt
patch
|
blob
|
history
raw
|
patch
|
inline
| side by side (parent:
37d07f8
)
diff --git
a/Documentation/user-manual.txt
b/Documentation/user-manual.txt
index 93a47b439b4504467fc5ba7612b8205367f347c2..f2b42068f3c0cfcd7e34aa46a2a83edd3dd6d587 100644
(file)
--- a/
Documentation/user-manual.txt
+++ b/
Documentation/user-manual.txt
@@
-1994,7
+1994,7
@@
$ git push ssh://yourserver.com/~you/proj.git +master
-------------------------------------------------
Normally whenever a branch head in a public repository is modified, it
-------------------------------------------------
Normally whenever a branch head in a public repository is modified, it
-is modified to point to a descend
e
nt of the commit that it pointed to
+is modified to point to a descend
a
nt of the commit that it pointed to
before. By forcing a push in this situation, you break that convention.
(See <<problems-with-rewriting-history>>.)
before. By forcing a push in this situation, you break that convention.
(See <<problems-with-rewriting-history>>.)
@@
-2921,7
+2921,7
@@
As you can see, a commit is defined by:
- a tree: The SHA1 name of a tree object (as defined below), representing
the contents of a directory at a certain point in time.
- parent(s): The SHA1 name of some number of commits which represent the
- a tree: The SHA1 name of a tree object (as defined below), representing
the contents of a directory at a certain point in time.
- parent(s): The SHA1 name of some number of commits which represent the
- immediately prev
oi
us step(s) in the history of the project. The
+ immediately prev
io
us step(s) in the history of the project. The
example above has one parent; merge commits may have more than
one. A commit with no parents is called a "root" commit, and
represents the initial revision of a project. Each project must have
example above has one parent; merge commits may have more than
one. A commit with no parents is called a "root" commit, and
represents the initial revision of a project. Each project must have
@@
-3242,7
+3242,7
@@
to replace them by hand. Back up your repository before attempting this
in case you corrupt things even more in the process.
We'll assume that the problem is a single missing or corrupted blob,
in case you corrupt things even more in the process.
We'll assume that the problem is a single missing or corrupted blob,
-which is sometimes a solv
e
able problem. (Recovering missing trees and
+which is sometimes a solvable problem. (Recovering missing trees and
especially commits is *much* harder).
Before starting, verify that there is corruption, and figure out where
especially commits is *much* harder).
Before starting, verify that there is corruption, and figure out where