From: "Martin Ågren" <martin.agren@gmail.com>
To: git@vger.kernel.org
Cc: Derrick Stolee <stolee@gmail.com>
Subject: [PATCH v2 0/4] git-commit-graph.txt: various cleanups
Date: Thu, 27 Sep 2018 21:12:18 +0200 [thread overview]
Message-ID: <cover.1538075326.git.martin.agren@gmail.com> (raw)
In-Reply-To: <6b1cb43e-a1a8-921f-cd66-3697609854e0@gmail.com>
This v2 starts with the same two patches as v1 did, then goes on to
change "[commit] graph file" to "commit-graph file" with a dash, to
match other instances as well as Derrick's feedback.
Martin Ågren (4):
git-commit-graph.txt: fix bullet lists
git-commit-graph.txt: typeset more in monospace
git-commit-graph.txt: refer to "*commit*-graph file"
Doc: refer to the "commit-graph file" with dash
Documentation/git-commit-graph.txt | 31 ++++++++++++------------
Documentation/technical/commit-graph.txt | 8 +++---
2 files changed, 20 insertions(+), 19 deletions(-)
Range-diff against v1:
1: 222721870b = 1: 837ef2f231 git-commit-graph.txt: fix bullet lists
2: acac5c3584 = 2: 9759a162ca git-commit-graph.txt: typeset more in monospace
3: 65f42c947a ! 3: 759bc886d8 git-commit-graph.txt: refer to "*commit* graph file"
@@ -1,17 +1,17 @@
Author: Martin Ågren <martin.agren@gmail.com>
- git-commit-graph.txt: refer to "*commit* graph file"
+ git-commit-graph.txt: refer to "*commit*-graph file"
- This document sometimes refers to the "commit graph file" as just "the
+ This document sometimes refers to the "commit-graph file" as just "the
graph file". This saves a couple of words here and there at the risk of
confusion. In particular, the documentation for `git commit-graph read`
appears to suggest that there are indeed different types of graph files.
Let's just write out the full name everywhere.
- The full name, by the way, is not the "commit-graph file" with a dash,
- cf. the synopsis. Use the dashless form. (The next commit will fix the
- remaining few instances of the "commit-graph file" in this document.)
+ The full name, by the way, is not the dash-less "commit graph file".
+ Use the dashed form. (The next commit will fix the remaining few
+ instances of the "commit graph file" in this document.)
Signed-off-by: Martin Ågren <martin.agren@gmail.com>
@@ -24,7 +24,7 @@
-Read a graph file given by the commit-graph file and output basic
-details about the graph file. Used for debugging purposes.
-+Read the commit graph file and output basic details about it.
++Read the commit-graph file and output basic details about it.
+Used for debugging purposes.
'verify'::
@@ -35,7 +35,7 @@
-* Write a graph file, extending the current graph file using commits
- in `<pack-index>`.
-+* Write a commit graph file, extending the current commit graph file
++* Write a commit-graph file, extending the current commit-graph file
+ using commits in `<pack-index>`.
+
------------------------------------------------
@@ -43,16 +43,14 @@
------------------------------------------------
-* Write a graph file containing all reachable commits.
-+* Write a commit graph file containing all reachable commits.
++* Write a commit-graph file containing all reachable commits.
+
------------------------------------------------
$ 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`.
-+* Write a commit graph file containing all commits in the current
-+ commit graph file along with those reachable from `HEAD`.
++* Write a commit-graph file containing all commits in the current
+ commit-graph file along with those reachable from `HEAD`.
+
------------------------------------------------
- $ git rev-parse HEAD | git commit-graph write --stdin-commits --append
4: fc81147ea4 < -: ---------- git-commit-graph.txt: refer to the "commit graph file" without dash
-: ---------- > 4: 99b64287ec Doc: refer to the "commit-graph file" with dash
--
2.19.0.216.g2d3b1c576c
next prev parent reply other threads:[~2018-09-27 19:12 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 ` [PATCH 2/4] git-commit-graph.txt: typeset more in monospace Martin Ågren
2018-09-19 23:29 ` 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 ` Martin Ågren [this message]
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cover.1538075326.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).