From: Derrick Stolee <stolee@gmail.com>
To: "Martin Ågren" <martin.agren@gmail.com>, git@vger.kernel.org
Subject: Re: [PATCH 3/4] git-commit-graph.txt: refer to "*commit* graph file"
Date: Wed, 19 Sep 2018 19:32:44 -0400 [thread overview]
Message-ID: <38803edb-de41-90db-33f6-f1a0d5344608@gmail.com> (raw)
In-Reply-To: <65f42c947aa2b392075740673a5dc889fd6e64e6.1537374062.git.martin.agren@gmail.com>
On 9/19/2018 12:30 PM, Martin Ågren wrote:
> 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.
This is a good idea. Let's be specific.
> 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 file is literally at ".git/objects/info/commit-graph" which is why I
tried to use "commit-graph" everywhere. Why do you think that "commit
graph" is better?
Thanks,
-Stolee
next prev parent reply other threads:[~2018-09-20 12:50 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 [this message]
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=38803edb-de41-90db-33f6-f1a0d5344608@gmail.com \
--to=stolee@gmail.com \
--cc=git@vger.kernel.org \
--cc=martin.agren@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).