{"thread":{"id":"6260","subject":"[PATCH] Documentation: tutorial editing","startedAt":"2007-01-07T03:38:38Z","lastAt":"2007-01-07T03:38:38Z","messageCount":1,"participants":["J. Bruce Fields"],"isPatch":true,"patchVersion":1,"patchTotal":null},"messages":[{"id":"31005","messageId":"20070107033838.GB9104@fieldses.org","threadId":"6260","inReplyTo":null,"subject":"[PATCH] Documentation: tutorial editing","fromName":"J. Bruce Fields","fromEmail":"bfields@fieldses.org","sentAt":"2007-01-07T03:38:38Z","receivedAt":"2007-01-07T03:38:38Z","isPatch":true,"sender":{"key":"bfields@citi.umich.edu","avatar":null},"body":"Edit for conciseness.\n\nAdd a \"Making changes\" section header.\n\nWhen possible, make sure that stuff in text boxes could be entered literally.\n(Don't use \"...\" unless we want a user to type that.)\n\nMove 'commit -a' example into a literal code section, clarify that it finds\nmodified files automatically.\n\nSigned-off-by: \"J. Bruce Fields\" <bfields@citi.umich.edu>\n---\n Documentation/tutorial.txt |   16 ++++++++++------\n 1 files changed, 10 insertions(+), 6 deletions(-)\n\ndiff --git a/Documentation/tutorial.txt b/Documentation/tutorial.txt\nindex 79884d9..2fdeed2 100644\n--- a/Documentation/tutorial.txt\n+++ b/Documentation/tutorial.txt\n@@ -43,8 +43,7 @@ Initialized empty Git repository in .git/\n \n You've now initialized the working directory--you may notice a new\n directory created, named \".git\".  Tell git that you want it to track\n-every file under the current directory with (notice the dot '.'\n-that means the current directory):\n+every file under the current directory (note the '.') with:\n \n ------------------------------------------------\n $ git add .\n@@ -59,6 +58,9 @@ $ git commit\n will prompt you for a commit message, then record the current state\n of all the files to the repository.\n \n+Making changes\n+--------------\n+\n Try modifying some files, then run\n \n ------------------------------------------------\n@@ -70,19 +72,21 @@ want the updated contents of these files in the commit and then\n make a commit, like this:\n \n ------------------------------------------------\n-$ git add file1 file...\n+$ git add file1 file2 file3\n $ git commit\n ------------------------------------------------\n \n This will again prompt your for a message describing the change, and then\n-record the new versions of the files you listed.  It is cumbersome\n-to list all files and you can say `git commit -a` (which stands for 'all')\n-instead of running `git add` beforehand.\n+record the new versions of the files you listed. \n+\n+Alternatively, instead of running `git add` beforehand, you can use\n \n ------------------------------------------------\n $ git commit -a\n ------------------------------------------------\n \n+which will automatically notice modified (but not new) files.\n+\n A note on commit messages: Though not required, it's a good idea to\n begin the commit message with a single short (less than 50 character)\n line summarizing the change, followed by a blank line and then a more\n-- \n1.5.0.rc0.ge16c2\n"}]}