summary | shortlog | log | commit | commitdiff | tree
raw | patch | inline | side by side (parent: 4c63ff4)
raw | patch | inline | side by side (parent: 4c63ff4)
author | J. Bruce Fields <bfields@citi.umich.edu> | |
Tue, 9 Jan 2007 02:59:42 +0000 (21:59 -0500) | ||
committer | J. Bruce Fields <bfields@citi.umich.edu> | |
Tue, 9 Jan 2007 02:59:42 +0000 (21:59 -0500) |
Add some more todo's for the user manual.
Signed-off-by: "J. Bruce Fields" <bfields@citi.umich.edu>
Signed-off-by: "J. Bruce Fields" <bfields@citi.umich.edu>
Documentation/user-manual.txt | patch | blob | history |
index b699c9b4e88374981717b44d768bede1d62d8c3a..a2fd5d27561a0893ab2ab95626729c1e34504256 100644 (file)
of temporary branch creation.
Explain how to refer to file stages in the "how to resolve a merge"
-section: diff -1, -2, -3, --ours, --theirs :1:/path notation.
+section: diff -1, -2, -3, --ours, --theirs :1:/path notation. The
+"git ls-files --unmerged --stage" thing is sorta useful too, actually. And
+note gitk --merge. Also what's easiest way to see common merge base?
+
+Add more good examples. Entire sections of just cookbook examples might be a
+good idea; maybe make an "advanced examples" section a standard end-of-chapter
+section?
Include cross-references to the glossary, where appropriate.
+Update for detached-head.
+
+Update for git-remote. Even if the command isn't there yet, I think we should
+probably just document the repository configuration necessary to set it up, as
+the default way to keep a repository up-to-date.
+
+To document:
+ reflogs, git reflog expire
+ shallow clones?? See draft 1.5.0 release notes for some documentation.