git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jon Loeliger <jdl@freescale.org>
To: git@vger.kernel.org
Subject: PATCH Suggestion for Tutorial Change
Date: Thu, 22 Sep 2005 10:51:57 -0500	[thread overview]
Message-ID: <E1EITMb-0001CX-D4@jdl.com> (raw)


In the tutorial, there is a section entitled "Checking it out"
that shows how to use diff log and whatchanged to insect some
of the repository state.

As the phrase "checkout" ususally carries some baggage WRT
other revision control mechanism, I suggest that we re-title
this section something like "Inspecting Changes".


Signed-off-by: Jon Loeliger <jdl@freescale.com>
---


diff --git a/Documentation/tutorial.txt b/Documentation/tutorial.txt
--- a/Documentation/tutorial.txt
+++ b/Documentation/tutorial.txt
@@ -432,8 +432,8 @@ message headers, and a few one-liners th
 commit itself (`git-commit`).


-Checking it out
----------------
+Inspecting Changes
+------------------

 While creating changes is useful, it's even more useful if you can tell
 later what changed. The most useful command for this is another of the

                 reply	other threads:[~2005-09-22 15:52 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=E1EITMb-0001CX-D4@jdl.com \
    --to=jdl@freescale.org \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).