git/list[1] front-page[2] threads[3] people[4] search[5] about
 

PATCH Suggestion for Tutorial Change

From
Jon Loeliger <jdl@freescale.org>
Date
Sep 22, 2005, 15:51 UTC
Message-ID
<E1EITMb-0001CX-D4@jdl.com>

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
Message 1 of 1 in “PATCH Suggestion for Tutorial Change”
  1. Jon LoeligerSep 22, 2005

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.