{"thread":{"id":"43747","subject":"[PATCH] Documentation: updates to \"Everyday GIT\"","startedAt":"2006-10-26T02:43:47Z","lastAt":"2006-10-26T02:43:47Z","messageCount":1,"participants":["J. Bruce Fields"],"isPatch":true,"patchVersion":1,"patchTotal":null},"messages":[{"id":"297723","messageId":"20061026024347.GB534@fieldses.org","threadId":"43747","inReplyTo":null,"subject":"[PATCH] Documentation: updates to \"Everyday GIT\"","fromName":"J. Bruce Fields","fromEmail":"bfields@fieldses.org","sentAt":"2006-10-26T02:43:47Z","receivedAt":"2006-10-26T02:43:47Z","isPatch":true,"sender":{"key":"bfields@citi.umich.edu","avatar":null},"body":"Remove the introduction: I think it should be obvious why\nwe have this.  (And if it isn't obvious then we've got other\nproblems.)\n\nReplace reference to git whatchanged by git log.\n\nMiscellaneous style and grammar fixes.\n\nSigned-off-by: J. Bruce Fields <bfields@citi.umich.edu>\n---\n Documentation/everyday.txt |   43 ++++++++++++-------------------------------\n 1 files changed, 12 insertions(+), 31 deletions(-)\n\ndiff --git a/Documentation/everyday.txt b/Documentation/everyday.txt\nindex b935c18..99e24a4 100644\n--- a/Documentation/everyday.txt\n+++ b/Documentation/everyday.txt\n@@ -1,22 +1,7 @@\n Everyday GIT With 20 Commands Or So\n ===================================\n \n-GIT suite has over 100 commands, and the manual page for each of\n-them discusses what the command does and how it is used in\n-detail, but until you know what command should be used in order\n-to achieve what you want to do, you cannot tell which manual\n-page to look at, and if you know that already you do not need\n-the manual.\n-\n-Does that mean you need to know all of them before you can use\n-git?  Not at all.  Depending on the role you play, the set of\n-commands you need to know is slightly different, but in any case\n-what you need to learn is far smaller than the full set of\n-commands to carry out your day-to-day work.  This document is to\n-serve as a cheat-sheet and a set of pointers for people playing\n-various roles.\n-\n-<<Basic Repository>> commands are needed by people who has a\n+<<Basic Repository>> commands are needed by people who have a\n repository --- that is everybody, because every working tree of\n git is a repository.\n \n@@ -25,28 +10,27 @@ essential for anybody who makes a commit\n works alone.\n \n If you work with other people, you will need commands listed in\n-<<Individual Developer (Participant)>> section as well.\n+the <<Individual Developer (Participant)>> section as well.\n \n-People who play <<Integrator>> role need to learn some more\n+People who play the <<Integrator>> role need to learn some more\n commands in addition to the above.\n \n <<Repository Administration>> commands are for system\n-administrators who are responsible to care and feed git\n-repositories to support developers.\n+administrators who are responsible for the care and feeding\n+of git repositories.\n \n \n Basic Repository[[Basic Repository]]\n ------------------------------------\n \n-Everybody uses these commands to feed and care git repositories.\n+Everybody uses these commands to maintain git repositories.\n \n   * gitlink:git-init-db[1] or gitlink:git-clone[1] to create a\n     new repository.\n \n-  * gitlink:git-fsck-objects[1] to validate the repository.\n+  * gitlink:git-fsck-objects[1] to check the repository for errors.\n \n-  * gitlink:git-prune[1] to garbage collect cruft in the\n-    repository.\n+  * gitlink:git-prune[1] to remove unused objects in the repository.\n \n   * gitlink:git-repack[1] to pack loose objects for efficiency.\n \n@@ -78,8 +62,8 @@ Repack a small project into single pack.\n $ git prune\n ------------\n +\n-<1> pack all the objects reachable from the refs into one pack\n-and remove unneeded other packs\n+<1> pack all the objects reachable from the refs into one pack,\n+then remove the other packs.\n \n \n Individual Developer (Standalone)[[Individual Developer (Standalone)]]\n@@ -93,9 +77,6 @@ following commands.\n \n   * gitlink:git-log[1] to see what happened.\n \n-  * gitlink:git-whatchanged[1] to find out where things have\n-    come from.\n-\n   * gitlink:git-checkout[1] and gitlink:git-branch[1] to switch\n     branches.\n \n@@ -120,7 +101,7 @@ following commands.\n Examples\n ~~~~~~~~\n \n-Extract a tarball and create a working tree and a new repository to keep track of it.::\n+Use a tarball as a starting point for a new repository:\n +\n ------------\n $ tar zxf frotz.tar.gz\n@@ -203,7 +184,7 @@ Clone the upstream and work on it.  Feed\n $ edit/compile/test; git commit -a -s <1>\n $ git format-patch origin <2>\n $ git pull <3>\n-$ git whatchanged -p ORIG_HEAD.. arch/i386 include/asm-i386 <4>\n+$ git log -p ORIG_HEAD.. arch/i386 include/asm-i386 <4>\n $ git pull git://git.kernel.org/pub/.../jgarzik/libata-dev.git ALL <5>\n $ git reset --hard ORIG_HEAD <6>\n $ git prune <7>\n-- \n1.4.3.2\n"}]}