{"thread":{"id":"4347","subject":"[PATCH 5/5] Documentation: fix a tutorial-2 typo","startedAt":"2006-05-29T23:31:32Z","lastAt":"2006-05-29T23:31:36Z","messageCount":5,"participants":["bfields@fieldses.org"],"isPatch":true,"patchVersion":1,"patchTotal":5},"messages":[{"id":"20940","messageId":"11489454961705-git-send-email-bfields@fieldses.org","threadId":"4347","inReplyTo":null,"subject":"[PATCH 1/5] documentation: mention gitk font adjustment in tutorial","fromName":"","fromEmail":"bfields@fieldses.org","sentAt":"2006-05-29T23:31:32Z","receivedAt":"2006-05-29T23:31:32Z","isPatch":true,"sender":{"key":"bfields@citi.umich.edu","avatar":null},"body":"From: J. Bruce Fields \n\nKind of silly, but the font I get by default in gitk makes it mostly\nunusable for me, so this is the first thing I'd want to know about.\n(But maybe there's a better suggestion than just Ctrl-='ing until\nsatisfied.)\n\nSigned-off-by: J. Bruce Fields \n\n---\n\nded59a62d1d7b114cdc4d5352e89006880e94f08\n Documentation/tutorial.txt | 4 +++-\n 1 files changed, 3 insertions(+), 1 deletions(-)\n\nded59a62d1d7b114cdc4d5352e89006880e94f08\ndiff --git a/Documentation/tutorial.txt b/Documentation/tutorial.txt\nindex 79781ad..5fdeab9 100644\n--- a/Documentation/tutorial.txt\n+++ b/Documentation/tutorial.txt\n@@ -429,7 +429,9 @@ visualizing their history. For example,\n -------------------------------------\n \n allows you to browse any commits from the last 2 weeks of commits\n-that modified files under the \"drivers\" directory.\n+that modified files under the \"drivers\" directory. (Note: you can\n+adjust gitk's fonts by holding down the control key while pressing\n+\"-\" or \"+\".)\n \n Finally, most commands that take filenames will optionally allow you\n to precede any filename by a commit, to specify a particular version\n-- \n1.3.3.gff62\n"},{"id":"20939","messageId":"1148945496592-git-send-email-bfields@fieldses.org","threadId":"4347","inReplyTo":"11489454961705-git-send-email-bfields@fieldses.org","subject":"[PATCH 2/5] documentation: add brief mention of cat-file to tutorial part I","fromName":"","fromEmail":"bfields@fieldses.org","sentAt":"2006-05-29T23:31:33Z","receivedAt":"2006-05-29T23:31:33Z","isPatch":true,"sender":{"key":"bfields@citi.umich.edu","avatar":null},"body":"From: J. Bruce Fields \n\nI'd rather avoid git cat-file so early on, but the\n\n\tgit-cat-file -p old-commit:/path/to/file\n\ntrick is too useful....\n\nAlso fix a nearby typo while we're at it.\n\nSigned-off-by: J. Bruce Fields \n\n---\n\ne47d8a459f0a2407304c9b7165b30746baa7fe29\n Documentation/tutorial.txt | 8 +++++++-\n 1 files changed, 7 insertions(+), 1 deletions(-)\n\ne47d8a459f0a2407304c9b7165b30746baa7fe29\ndiff --git a/Documentation/tutorial.txt b/Documentation/tutorial.txt\nindex 5fdeab9..039a859 100644\n--- a/Documentation/tutorial.txt\n+++ b/Documentation/tutorial.txt\n@@ -435,12 +435,18 @@ adjust gitk's fonts by holding down the \n \n Finally, most commands that take filenames will optionally allow you\n to precede any filename by a commit, to specify a particular version\n-fo the file:\n+of the file:\n \n -------------------------------------\n $ git diff v2.5:Makefile HEAD:Makefile.in\n -------------------------------------\n \n+You can also use \"git cat-file -p\" to see any such file:\n+\n+-------------------------------------\n+$ git cat-file -p v2.5:Makefile\n+-------------------------------------\n+\n Next Steps\n ----------\n \n-- \n1.3.3.gff62\n"},{"id":"20938","messageId":"11489454963995-git-send-email-bfields@fieldses.org","threadId":"4347","inReplyTo":"1148945496592-git-send-email-bfields@fieldses.org","subject":"[PATCH 3/5] Documentation: retitle the git-core tutorial","fromName":"","fromEmail":"bfields@fieldses.org","sentAt":"2006-05-29T23:31:34Z","receivedAt":"2006-05-29T23:31:34Z","isPatch":true,"sender":{"key":"bfields@citi.umich.edu","avatar":null},"body":"From: J. Bruce Fields \n\nGive the git-core tutorial a name that better reflects its intended\naudience.\n\nSigned-off-by: J. Bruce Fields \n\n---\n\ncbec3d5696e6c9fa5a44046e1cd1c870681c6897\n Documentation/core-tutorial.txt | 4 ++--\n 1 files changed, 2 insertions(+), 2 deletions(-)\n\ncbec3d5696e6c9fa5a44046e1cd1c870681c6897\ndiff --git a/Documentation/core-tutorial.txt b/Documentation/core-tutorial.txt\nindex d1360ec..5a831ad 100644\n--- a/Documentation/core-tutorial.txt\n+++ b/Documentation/core-tutorial.txt\n@@ -1,5 +1,5 @@\n-A short git tutorial\n-====================\n+A git core tutorial for developers\n+==================================\n \n Introduction\n ------------\n-- \n1.3.3.gff62\n"},{"id":"20937","messageId":"11489454963586-git-send-email-bfields@fieldses.org","threadId":"4347","inReplyTo":"11489454963995-git-send-email-bfields@fieldses.org","subject":"[PATCH 4/5] Documentation: rewrite the core-tutorial introduction","fromName":"","fromEmail":"bfields@fieldses.org","sentAt":"2006-05-29T23:31:35Z","receivedAt":"2006-05-29T23:31:35Z","isPatch":true,"sender":{"key":"bfields@citi.umich.edu","avatar":null},"body":"From: J. Bruce Fields \n\nRevise for conciseness, clarify the intended audience.\n\nSigned-off-by: J. Bruce Fields \n\n---\n\n3bb93812a96e602729e52ab1ac5a555f453470be\n Documentation/core-tutorial.txt | 30 +++++++++---------------------\n 1 files changed, 9 insertions(+), 21 deletions(-)\n\n3bb93812a96e602729e52ab1ac5a555f453470be\ndiff --git a/Documentation/core-tutorial.txt b/Documentation/core-tutorial.txt\nindex 5a831ad..3ab3317 100644\n--- a/Documentation/core-tutorial.txt\n+++ b/Documentation/core-tutorial.txt\n@@ -4,35 +4,23 @@ A git core tutorial for developers\n Introduction\n ------------\n \n-This is trying to be a short tutorial on setting up and using a git\n-repository, mainly because being hands-on and using explicit examples is\n-often the best way of explaining what is going on.\n+If you primarily interested in using git to manage your own projects,\n+see link:tutorial.txt[A tutorial introduction to git] before reading\n+this.\n \n-In normal life, most people wouldn't use the \"core\" git programs\n-directly, but rather script around them to make them more palatable. \n-Understanding the core git stuff may help some people get those scripts\n-done, though, and it may also be instructive in helping people\n-understand what it is that the higher-level helper scripts are actually\n-doing. \n+However, git also provides commands that provide low-level access to\n+git internals. These \"core\" git commands will be useful to advanced\n+users, to git hackers, and to anyone developing software on top of\n+the git core.\n \n The core git is often called \"plumbing\", with the prettier user\n interfaces on top of it called \"porcelain\". You may not want to use the\n plumbing directly very often, but it can be good to know what the\n plumbing does for when the porcelain isn't flushing.\n \n-The material presented here often goes deep describing how things\n-work internally. If you are mostly interested in using git as a\n-SCM, you can skip them during your first pass.\n-\n-[NOTE]\n-And those \"too deep\" descriptions are often marked as Note.\n-\n [NOTE]\n-If you are already familiar with another version control system,\n-like CVS, you may want to take a look at\n-link:everyday.html[Everyday GIT in 20 commands or so] first\n-before reading this.\n-\n+Notes like this mark descriptions of deep git internals that can\n+be skipped on a first reading.\n \n Creating a git repository\n -------------------------\n-- \n1.3.3.gff62\n"},{"id":"20936","messageId":"11489454963791-git-send-email-bfields@fieldses.org","threadId":"4347","inReplyTo":"11489454963586-git-send-email-bfields@fieldses.org","subject":"[PATCH 5/5] Documentation: fix a tutorial-2 typo","fromName":"","fromEmail":"bfields@fieldses.org","sentAt":"2006-05-29T23:31:36Z","receivedAt":"2006-05-29T23:31:36Z","isPatch":true,"sender":{"key":"bfields@citi.umich.edu","avatar":null},"body":"From: J. Bruce Fields \n\nFix a typo.\n\nSigned-off-by: J. Bruce Fields \n\n---\n\n2506b48d2aee595a5023d31166a64d4d28bf8789\n Documentation/tutorial-2.txt | 2 +-\n 1 files changed, 1 insertions(+), 1 deletions(-)\n\n2506b48d2aee595a5023d31166a64d4d28bf8789\ndiff --git a/Documentation/tutorial-2.txt b/Documentation/tutorial-2.txt\nindex 08d3453..9c9500c 100644\n--- a/Documentation/tutorial-2.txt\n+++ b/Documentation/tutorial-2.txt\n@@ -377,7 +377,7 @@ At this point you should know everything\n pages for any of the git commands; one good place to start would be\n with the commands mentioned in link:everyday.html[Everyday git]. You\n should be able to find any unknown jargon in the\n-link:glossary.html[Glosssay].\n+link:glossary.html[Glossary].\n \n The link:cvs-migration.html[CVS migration] document explains how to\n import a CVS repository into git, and shows how to use git in a\n-- \n1.3.3.gff62\n"}]}