git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Martin Ågren" <martin.agren@gmail.com>
To: git@vger.kernel.org
Cc: Derrick Stolee <stolee@gmail.com>
Subject: [PATCH 2/4] git-commit-graph.txt: typeset more in monospace
Date: Wed, 19 Sep 2018 18:30:33 +0200	[thread overview]
Message-ID: <acac5c3584b1cc7cf36ce4f7800738548eba8ccb.1537374062.git.martin.agren@gmail.com> (raw)
In-Reply-To: <cover.1537374062.git.martin.agren@gmail.com>

While we're here, fix an instance of "folder" to be "directory".

Signed-off-by: Martin Ågren <martin.agren@gmail.com>
---
 Documentation/git-commit-graph.txt | 13 +++++++------
 1 file changed, 7 insertions(+), 6 deletions(-)

diff --git a/Documentation/git-commit-graph.txt b/Documentation/git-commit-graph.txt
index f42f2a1481..6ac610f016 100644
--- a/Documentation/git-commit-graph.txt
+++ b/Documentation/git-commit-graph.txt
@@ -25,9 +25,9 @@ OPTIONS
 --object-dir::
 	Use given directory for the location of packfiles and commit graph
 	file. This parameter exists to specify the location of an alternate
-	that only has the objects directory, not a full .git directory. The
-	commit graph file is expected to be at <dir>/info/commit-graph and
-	the packfiles are expected to be in <dir>/pack.
+	that only has the objects directory, not a full `.git` directory. The
+	commit graph file is expected to be at `<dir>/info/commit-graph` and
+	the packfiles are expected to be in `<dir>/pack`.
 
 
 COMMANDS
@@ -66,14 +66,15 @@ database. Used to check for corrupted data.
 EXAMPLES
 --------
 
-* Write a commit graph file for the packed commits in your local .git folder.
+* Write a commit graph file for the packed commits in your local `.git`
+  directory.
 +
 ------------------------------------------------
 $ git commit-graph write
 ------------------------------------------------
 
 * Write a graph file, extending the current graph file using commits
-  in <pack-index>.
+  in `<pack-index>`.
 +
 ------------------------------------------------
 $ echo <pack-index> | git commit-graph write --stdin-packs
@@ -86,7 +87,7 @@ $ git show-ref -s | git commit-graph write --stdin-commits
 ------------------------------------------------
 
 * Write a graph file containing all commits in the current
-  commit-graph file along with those reachable from HEAD.
+  commit-graph file along with those reachable from `HEAD`.
 +
 ------------------------------------------------
 $ git rev-parse HEAD | git commit-graph write --stdin-commits --append
-- 
2.19.0.216.g2d3b1c576c


  parent reply	other threads:[~2018-09-19 16:30 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-19 16:30 [PATCH 0/4] git-commit-graph.txt: various cleanups Martin Ågren
2018-09-19 16:30 ` [PATCH 1/4] git-commit-graph.txt: fix bullet lists Martin Ågren
2018-09-19 23:28   ` Derrick Stolee
2018-09-19 16:30 ` Martin Ågren [this message]
2018-09-19 23:29   ` [PATCH 2/4] git-commit-graph.txt: typeset more in monospace Derrick Stolee
2018-09-19 16:30 ` [PATCH 3/4] git-commit-graph.txt: refer to "*commit* graph file" Martin Ågren
2018-09-19 23:32   ` Derrick Stolee
2018-09-20 13:38     ` Martin Ågren
2018-09-20 13:42       ` Derrick Stolee
2018-09-27 19:12         ` [PATCH v2 0/4] git-commit-graph.txt: various cleanups Martin Ågren
2018-09-27 19:12           ` [PATCH v2 1/4] git-commit-graph.txt: fix bullet lists Martin Ågren
2018-09-27 19:12           ` [PATCH v2 2/4] git-commit-graph.txt: typeset more in monospace Martin Ågren
2018-09-27 19:12           ` [PATCH v2 3/4] git-commit-graph.txt: refer to "*commit*-graph file" Martin Ågren
2018-09-27 19:12           ` [PATCH v2 4/4] Doc: refer to the "commit-graph file" with dash Martin Ågren
2018-09-27 19:16           ` [PATCH v2 0/4] git-commit-graph.txt: various cleanups Derrick Stolee
2018-09-27 19:21             ` Martin Ågren
2018-09-19 16:30 ` [PATCH 4/4] git-commit-graph.txt: refer to the "commit graph file" without dash Martin Ågren

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=acac5c3584b1cc7cf36ce4f7800738548eba8ccb.1537374062.git.martin.agren@gmail.com \
    --to=martin.agren@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=stolee@gmail.com \
    /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).