{"thread":{"id":"49383","subject":"[PATCH 0/4] git-commit-graph.txt: various cleanups","startedAt":"2018-09-19T16:30:48Z","lastAt":"2018-09-27T19:21:45Z","messageCount":17,"participants":["Martin Ågren","Derrick Stolee"],"isPatch":true,"patchVersion":1,"patchTotal":4},"messages":[{"id":"358458","messageId":"cover.1537374062.git.martin.agren@gmail.com","threadId":"49383","inReplyTo":null,"subject":"[PATCH 0/4] git-commit-graph.txt: various cleanups","fromName":"Martin Ågren","fromEmail":"martin.agren@gmail.com","sentAt":"2018-09-19T16:30:31Z","receivedAt":"2018-09-19T16:30:48Z","isPatch":true,"sender":{"key":"martin.agren@gmail.com","avatar":null},"body":"The first patch is a bug-fix. The second applies some more\n`monospace`-ing, which should also be good thing.\n\nThe last two patches are based on my understanding that `git\ncommit-graph` handles the \"commit graph file\", without a dash. If that's\ncorrect, there might be more such cleanups to be made in other parts of\ngit.git. If the dash should actually be there, I could do these changes\nin the other direction. Or maybe dash-vs-no-dash is not an actual\nproblem at all...\n\nMartin\n\nMartin Ågren (4):\n git-commit-graph.txt: fix bullet lists\n git-commit-graph.txt: typeset more in monospace\n git-commit-graph.txt: refer to \"*commit* graph file\"\n git-commit-graph.txt: refer to the \"commit graph file\" without dash\n\n Documentation/git-commit-graph.txt | 29 +++++++++++++++--------------\n 1 file changed, 15 insertions(+), 14 deletions(-)\n\n-- \n2.19.0.216.g2d3b1c576c\n\n"},{"id":"358459","messageId":"222721870b74742fd2fd20816a8e351b28e788cc.1537374062.git.martin.agren@gmail.com","threadId":"49383","inReplyTo":"cover.1537374062.git.martin.agren@gmail.com","subject":"[PATCH 1/4] git-commit-graph.txt: fix bullet lists","fromName":"Martin Ågren","fromEmail":"martin.agren@gmail.com","sentAt":"2018-09-19T16:30:32Z","receivedAt":"2018-09-19T16:30:51Z","isPatch":true,"sender":{"key":"martin.agren@gmail.com","avatar":null},"body":"We have a couple of bullet items which span multiple lines, and where we\nhave prefixed each line with a `*`. (This might be the result of a text\neditor trying to help.) This results in each line being typeset as a\nseparate bullet item. Drop the extra `*`.\n\nSigned-off-by: Martin Ågren \n---\n Documentation/git-commit-graph.txt | 4 ++--\n 1 file changed, 2 insertions(+), 2 deletions(-)\n\ndiff --git a/Documentation/git-commit-graph.txt b/Documentation/git-commit-graph.txt\nindex dececb79d7..f42f2a1481 100644\n--- a/Documentation/git-commit-graph.txt\n+++ b/Documentation/git-commit-graph.txt\n@@ -73,7 +73,7 @@ $ git commit-graph write\n ------------------------------------------------\n \n * Write a graph file, extending the current graph file using commits\n-* in .\n+ in .\n +\n ------------------------------------------------\n $ echo | git commit-graph write --stdin-packs\n@@ -86,7 +86,7 @@ $ git show-ref -s | git commit-graph write --stdin-commits\n ------------------------------------------------\n \n * Write a graph file containing all commits in the current\n-* commit-graph file along with those reachable from HEAD.\n+ commit-graph file along with those reachable from HEAD.\n +\n ------------------------------------------------\n $ git rev-parse HEAD | git commit-graph write --stdin-commits --append\n-- \n2.19.0.216.g2d3b1c576c\n\n"},{"id":"358460","messageId":"acac5c3584b1cc7cf36ce4f7800738548eba8ccb.1537374062.git.martin.agren@gmail.com","threadId":"49383","inReplyTo":"cover.1537374062.git.martin.agren@gmail.com","subject":"[PATCH 2/4] git-commit-graph.txt: typeset more in monospace","fromName":"Martin Ågren","fromEmail":"martin.agren@gmail.com","sentAt":"2018-09-19T16:30:33Z","receivedAt":"2018-09-19T16:30:53Z","isPatch":true,"sender":{"key":"martin.agren@gmail.com","avatar":null},"body":"While we're here, fix an instance of \"folder\" to be \"directory\".\n\nSigned-off-by: Martin Ågren \n---\n Documentation/git-commit-graph.txt | 13 +++++++------\n 1 file changed, 7 insertions(+), 6 deletions(-)\n\ndiff --git a/Documentation/git-commit-graph.txt b/Documentation/git-commit-graph.txt\nindex f42f2a1481..6ac610f016 100644\n--- a/Documentation/git-commit-graph.txt\n+++ b/Documentation/git-commit-graph.txt\n@@ -25,9 +25,9 @@ OPTIONS\n --object-dir::\n \tUse given directory for the location of packfiles and commit graph\n \tfile. This parameter exists to specify the location of an alternate\n-\tthat only has the objects directory, not a full .git directory. The\n-\tcommit graph file is expected to be at /info/commit-graph and\n-\tthe packfiles are expected to be in /pack.\n+\tthat only has the objects directory, not a full `.git` directory. The\n+\tcommit graph file is expected to be at `/info/commit-graph` and\n+\tthe packfiles are expected to be in `/pack`.\n \n \n COMMANDS\n@@ -66,14 +66,15 @@ database. Used to check for corrupted data.\n EXAMPLES\n --------\n \n-* Write a commit graph file for the packed commits in your local .git folder.\n+* Write a commit graph file for the packed commits in your local `.git`\n+ directory.\n +\n ------------------------------------------------\n $ git commit-graph write\n ------------------------------------------------\n \n * Write a graph file, extending the current graph file using commits\n- in .\n+ in ``.\n +\n ------------------------------------------------\n $ echo | git commit-graph write --stdin-packs\n@@ -86,7 +87,7 @@ $ git show-ref -s | git commit-graph write --stdin-commits\n ------------------------------------------------\n \n * Write a graph file containing all commits in the current\n- commit-graph file along with those reachable from HEAD.\n+ commit-graph file along with those reachable from `HEAD`.\n +\n ------------------------------------------------\n $ git rev-parse HEAD | git commit-graph write --stdin-commits --append\n-- \n2.19.0.216.g2d3b1c576c\n\n"},{"id":"358461","messageId":"65f42c947aa2b392075740673a5dc889fd6e64e6.1537374062.git.martin.agren@gmail.com","threadId":"49383","inReplyTo":"cover.1537374062.git.martin.agren@gmail.com","subject":"[PATCH 3/4] git-commit-graph.txt: refer to \"*commit* graph file\"","fromName":"Martin Ågren","fromEmail":"martin.agren@gmail.com","sentAt":"2018-09-19T16:30:34Z","receivedAt":"2018-09-19T16:30:55Z","isPatch":true,"sender":{"key":"martin.agren@gmail.com","avatar":null},"body":"This document sometimes refers to the \"commit graph file\" as just \"the\ngraph file\". This saves a couple of words here and there at the risk of\nconfusion. In particular, the documentation for `git commit-graph read`\nappears to suggest that there are indeed different types of graph files.\n\nLet's just write out the full name everywhere.\n\nThe full name, by the way, is not the \"commit-graph file\" with a dash,\ncf. the synopsis. Use the dashless form. (The next commit will fix the\nremaining few instances of the \"commit-graph file\" in this document.)\n\nSigned-off-by: Martin Ågren \n---\n Documentation/git-commit-graph.txt | 14 +++++++-------\n 1 file changed, 7 insertions(+), 7 deletions(-)\n\ndiff --git a/Documentation/git-commit-graph.txt b/Documentation/git-commit-graph.txt\nindex 6ac610f016..55f63d47d9 100644\n--- a/Documentation/git-commit-graph.txt\n+++ b/Documentation/git-commit-graph.txt\n@@ -54,8 +54,8 @@ existing commit-graph file.\n \n 'read'::\n \n-Read a graph file given by the commit-graph file and output basic\n-details about the graph file. Used for debugging purposes.\n+Read the commit graph file and output basic details about it.\n+Used for debugging purposes.\n \n 'verify'::\n \n@@ -73,21 +73,21 @@ EXAMPLES\n $ git commit-graph write\n ------------------------------------------------\n \n-* Write a graph file, extending the current graph file using commits\n- in ``.\n+* Write a commit graph file, extending the current commit graph file\n+ using commits in ``.\n +\n ------------------------------------------------\n $ echo | git commit-graph write --stdin-packs\n ------------------------------------------------\n \n-* Write a graph file containing all reachable commits.\n+* Write a commit graph file containing all reachable commits.\n +\n ------------------------------------------------\n $ git show-ref -s | git commit-graph write --stdin-commits\n ------------------------------------------------\n \n-* Write a graph file containing all commits in the current\n- commit-graph file along with those reachable from `HEAD`.\n+* Write a commit graph file containing all commits in the current\n+ commit graph file along with those reachable from `HEAD`.\n +\n ------------------------------------------------\n $ git rev-parse HEAD | git commit-graph write --stdin-commits --append\n-- \n2.19.0.216.g2d3b1c576c\n\n"},{"id":"358462","messageId":"fc81147ea42e382a3197c850830fe2142eda148e.1537374062.git.martin.agren@gmail.com","threadId":"49383","inReplyTo":"cover.1537374062.git.martin.agren@gmail.com","subject":"[PATCH 4/4] git-commit-graph.txt: refer to the \"commit graph file\" without dash","fromName":"Martin Ågren","fromEmail":"martin.agren@gmail.com","sentAt":"2018-09-19T16:30:35Z","receivedAt":"2018-09-19T16:30:59Z","isPatch":true,"sender":{"key":"martin.agren@gmail.com","avatar":null},"body":"The command is `git commit-graph`, but the file it processes is the\n\"commit graph file\" without a dash. We have a few references to the\n\"commit-graph file\", though. Fix them.\n\nSigned-off-by: Martin Ågren \n---\n Documentation/git-commit-graph.txt | 6 +++---\n 1 file changed, 3 insertions(+), 3 deletions(-)\n\ndiff --git a/Documentation/git-commit-graph.txt b/Documentation/git-commit-graph.txt\nindex 55f63d47d9..dd0a53736f 100644\n--- a/Documentation/git-commit-graph.txt\n+++ b/Documentation/git-commit-graph.txt\n@@ -50,7 +50,7 @@ commits starting at all refs. (Cannot be combined with `--stdin-commits`\n or `--stdin-packs`.)\n +\n With the `--append` option, include all commits that are present in the\n-existing commit-graph file.\n+existing commit graph file.\n \n 'read'::\n \n@@ -59,7 +59,7 @@ Used for debugging purposes.\n \n 'verify'::\n \n-Read the commit-graph file and verify its contents against the object\n+Read the commit graph file and verify its contents against the object\n database. Used to check for corrupted data.\n \n \n@@ -93,7 +93,7 @@ $ git show-ref -s | git commit-graph write --stdin-commits\n $ git rev-parse HEAD | git commit-graph write --stdin-commits --append\n ------------------------------------------------\n \n-* Read basic information from the commit-graph file.\n+* Read basic information from the commit graph file.\n +\n ------------------------------------------------\n $ git commit-graph read\n-- \n2.19.0.216.g2d3b1c576c\n\n"},{"id":"358502","messageId":"84a8fa75-0f3f-878a-ca5f-132e7ca4f196@gmail.com","threadId":"49383","inReplyTo":"222721870b74742fd2fd20816a8e351b28e788cc.1537374062.git.martin.agren@gmail.com","subject":"Re: [PATCH 1/4] git-commit-graph.txt: fix bullet lists","fromName":"Derrick Stolee","fromEmail":"stolee@gmail.com","sentAt":"2018-09-19T23:28:45Z","receivedAt":"2018-09-20T12:50:50Z","isPatch":true,"sender":{"key":"stolee@gmail.com","avatar":"https://avatars.githubusercontent.com/u/570044?v=4"},"body":"On 9/19/2018 12:30 PM, Martin Ågren wrote:\n> We have a couple of bullet items which span multiple lines, and where we\n> have prefixed each line with a `*`. (This might be the result of a text\n> editor trying to help.) This results in each line being typeset as a\n> separate bullet item. Drop the extra `*`.\n\nThank you for noticing this. It clearly looks wrong at \nhttps://git-scm.com/docs/git-commit-graph\n\n-Stolee\n"},{"id":"358503","messageId":"ced54c95-b323-2c04-e612-eb987c8d9c02@gmail.com","threadId":"49383","inReplyTo":"acac5c3584b1cc7cf36ce4f7800738548eba8ccb.1537374062.git.martin.agren@gmail.com","subject":"Re: [PATCH 2/4] git-commit-graph.txt: typeset more in monospace","fromName":"Derrick Stolee","fromEmail":"stolee@gmail.com","sentAt":"2018-09-19T23:29:33Z","receivedAt":"2018-09-20T12:50:53Z","isPatch":true,"sender":{"key":"stolee@gmail.com","avatar":"https://avatars.githubusercontent.com/u/570044?v=4"},"body":"On 9/19/2018 12:30 PM, Martin Ågren wrote:\n> While we're here, fix an instance of \"folder\" to be \"directory\".\n\nThese changes are clearly good. Thanks!\n"},{"id":"358504","messageId":"38803edb-de41-90db-33f6-f1a0d5344608@gmail.com","threadId":"49383","inReplyTo":"65f42c947aa2b392075740673a5dc889fd6e64e6.1537374062.git.martin.agren@gmail.com","subject":"Re: [PATCH 3/4] git-commit-graph.txt: refer to \"*commit* graph file\"","fromName":"Derrick Stolee","fromEmail":"stolee@gmail.com","sentAt":"2018-09-19T23:32:44Z","receivedAt":"2018-09-20T12:50:58Z","isPatch":true,"sender":{"key":"stolee@gmail.com","avatar":"https://avatars.githubusercontent.com/u/570044?v=4"},"body":"On 9/19/2018 12:30 PM, Martin Ågren wrote:\n> This document sometimes refers to the \"commit graph file\" as just \"the\n> graph file\". This saves a couple of words here and there at the risk of\n> confusion. In particular, the documentation for `git commit-graph read`\n> appears to suggest that there are indeed different types of graph files.\n>\n> Let's just write out the full name everywhere.\nThis is a good idea. Let's be specific.\n> The full name, by the way, is not the \"commit-graph file\" with a dash,\n> cf. the synopsis. Use the dashless form. (The next commit will fix the\n> remaining few instances of the \"commit-graph file\" in this document.)\n\nThe file is literally at \".git/objects/info/commit-graph\" which is why I \ntried to use \"commit-graph\" everywhere. Why do you think that \"commit \ngraph\" is better?\n\nThanks,\n-Stolee\n"},{"id":"358508","messageId":"CAN0heSo89WS69VXuPp02nQizordMWgNG0D0o-f-tm02Tp_gGEw@mail.gmail.com","threadId":"49383","inReplyTo":"38803edb-de41-90db-33f6-f1a0d5344608@gmail.com","subject":"Re: [PATCH 3/4] git-commit-graph.txt: refer to \"*commit* graph file\"","fromName":"Martin Ågren","fromEmail":"martin.agren@gmail.com","sentAt":"2018-09-20T13:38:44Z","receivedAt":"2018-09-20T13:39:01Z","isPatch":true,"sender":{"key":"martin.agren@gmail.com","avatar":null},"body":"On Thu, 20 Sep 2018 at 14:50, Derrick Stolee wrote:\n>\n> On 9/19/2018 12:30 PM, Martin Ågren wrote:\n> > The full name, by the way, is not the \"commit-graph file\" with a dash,\n> > cf. the synopsis. Use the dashless form. (The next commit will fix the\n> > remaining few instances of the \"commit-graph file\" in this document.)\n>\n> The file is literally at \".git/objects/info/commit-graph\" which is why I\n> tried to use \"commit-graph\" everywhere. Why do you think that \"commit\n> graph\" is better?\n\nI noticed the discrepancy between \"commit graph file\" and \"commit-graph\nfile\" and briefly wondered if it was intentional, i.e., if it meant\nanything, but the dash vs no dash seemed pretty random to me. In order\nto figure out which was (more) correct, I went to the synopsis. But\nadmittedly, that was quite arbitrary. For all I know, \"the commit-graph\nfile\" could be the better choice, grammatically.\n\nThere is the file named \"commit-graph\" as you note, but it might on the\nother hand just as well be called \"cg.bin\". I would probably try to let\nthe filename \"commit-graph\" influence the user manual only if we would\nhave written \"cg.bin\" instead. For example, if we would talk about how\nyou might get out of a hole by deleting the \"<...>/commit-graph\"\n(\"cg.bin\") file manually.\n\nBut that's certainly not to argue against \"the commit-graph file\". I'd\nbe happy to s/commit graph file/commit-graph file/g instead to keep\nothers from wondering if these are two slightly different things. And\nif the concept and the file have the same name, all the better.\n\nIf you agree, I'll do that in a v2, where I will also note in the\nOptions section that `--object-dir` takes a ``.\n\nMartin\n"},{"id":"358509","messageId":"6b1cb43e-a1a8-921f-cd66-3697609854e0@gmail.com","threadId":"49383","inReplyTo":"CAN0heSo89WS69VXuPp02nQizordMWgNG0D0o-f-tm02Tp_gGEw@mail.gmail.com","subject":"Re: [PATCH 3/4] git-commit-graph.txt: refer to \"*commit* graph file\"","fromName":"Derrick Stolee","fromEmail":"stolee@gmail.com","sentAt":"2018-09-20T13:42:00Z","receivedAt":"2018-09-20T13:42:06Z","isPatch":true,"sender":{"key":"stolee@gmail.com","avatar":"https://avatars.githubusercontent.com/u/570044?v=4"},"body":"On 9/20/2018 9:38 AM, Martin Ågren wrote:\n> On Thu, 20 Sep 2018 at 14:50, Derrick Stolee wrote:\n>> On 9/19/2018 12:30 PM, Martin Ågren wrote:\n>>> The full name, by the way, is not the \"commit-graph file\" with a dash,\n>>> cf. the synopsis. Use the dashless form. (The next commit will fix the\n>>> remaining few instances of the \"commit-graph file\" in this document.)\n>> The file is literally at \".git/objects/info/commit-graph\" which is why I\n>> tried to use \"commit-graph\" everywhere. Why do you think that \"commit\n>> graph\" is better?\n> I noticed the discrepancy between \"commit graph file\" and \"commit-graph\n> file\" and briefly wondered if it was intentional, i.e., if it meant\n> anything, but the dash vs no dash seemed pretty random to me. In order\n> to figure out which was (more) correct, I went to the synopsis. But\n> admittedly, that was quite arbitrary. For all I know, \"the commit-graph\n> file\" could be the better choice, grammatically.\n\nYeah, the fact that I was inconsistent forced you to make a choice. \nSorry for that.\n\n> There is the file named \"commit-graph\" as you note, but it might on the\n> other hand just as well be called \"cg.bin\". I would probably try to let\n> the filename \"commit-graph\" influence the user manual only if we would\n> have written \"cg.bin\" instead. For example, if we would talk about how\n> you might get out of a hole by deleting the \"<...>/commit-graph\"\n> (\"cg.bin\") file manually.\n>\n> But that's certainly not to argue against \"the commit-graph file\". I'd\n> be happy to s/commit graph file/commit-graph file/g instead to keep\n> others from wondering if these are two slightly different things. And\n> if the concept and the file have the same name, all the better.\n>\n> If you agree, I'll do that in a v2, where I will also note in the\n> Options section that `--object-dir` takes a ``.\nI think \"commit-graph\" is better. Thanks for also catching the `...` \nformatting.\n\nThanks!\n-Stolee\n"},{"id":"359093","messageId":"cover.1538075326.git.martin.agren@gmail.com","threadId":"49383","inReplyTo":"6b1cb43e-a1a8-921f-cd66-3697609854e0@gmail.com","subject":"[PATCH v2 0/4] git-commit-graph.txt: various cleanups","fromName":"Martin Ågren","fromEmail":"martin.agren@gmail.com","sentAt":"2018-09-27T19:12:18Z","receivedAt":"2018-09-27T19:12:43Z","isPatch":true,"sender":{"key":"martin.agren@gmail.com","avatar":null},"body":"This v2 starts with the same two patches as v1 did, then goes on to\nchange \"[commit] graph file\" to \"commit-graph file\" with a dash, to\nmatch other instances as well as Derrick's feedback.\n\nMartin Ågren (4):\n git-commit-graph.txt: fix bullet lists\n git-commit-graph.txt: typeset more in monospace\n git-commit-graph.txt: refer to \"*commit*-graph file\"\n Doc: refer to the \"commit-graph file\" with dash\n\n Documentation/git-commit-graph.txt | 31 ++++++++++++------------\n Documentation/technical/commit-graph.txt | 8 +++---\n 2 files changed, 20 insertions(+), 19 deletions(-)\n\nRange-diff against v1:\n1: 222721870b = 1: 837ef2f231 git-commit-graph.txt: fix bullet lists\n2: acac5c3584 = 2: 9759a162ca git-commit-graph.txt: typeset more in monospace\n3: 65f42c947a ! 3: 759bc886d8 git-commit-graph.txt: refer to \"*commit* graph file\"\n @@ -1,17 +1,17 @@\n Author: Martin Ågren \n \n - git-commit-graph.txt: refer to \"*commit* graph file\"\n + git-commit-graph.txt: refer to \"*commit*-graph file\"\n \n - This document sometimes refers to the \"commit graph file\" as just \"the\n + This document sometimes refers to the \"commit-graph file\" as just \"the\n graph file\". This saves a couple of words here and there at the risk of\n confusion. In particular, the documentation for `git commit-graph read`\n appears to suggest that there are indeed different types of graph files.\n \n Let's just write out the full name everywhere.\n \n - The full name, by the way, is not the \"commit-graph file\" with a dash,\n - cf. the synopsis. Use the dashless form. (The next commit will fix the\n - remaining few instances of the \"commit-graph file\" in this document.)\n + The full name, by the way, is not the dash-less \"commit graph file\".\n + Use the dashed form. (The next commit will fix the remaining few\n + instances of the \"commit graph file\" in this document.)\n \n Signed-off-by: Martin Ågren \n \n @@ -24,7 +24,7 @@\n \n -Read a graph file given by the commit-graph file and output basic\n -details about the graph file. Used for debugging purposes.\n -+Read the commit graph file and output basic details about it.\n ++Read the commit-graph file and output basic details about it.\n +Used for debugging purposes.\n \n 'verify'::\n @@ -35,7 +35,7 @@\n \n -* Write a graph file, extending the current graph file using commits\n - in ``.\n -+* Write a commit graph file, extending the current commit graph file\n ++* Write a commit-graph file, extending the current commit-graph file\n + using commits in ``.\n +\n ------------------------------------------------\n @@ -43,16 +43,14 @@\n ------------------------------------------------\n \n -* Write a graph file containing all reachable commits.\n -+* Write a commit graph file containing all reachable commits.\n ++* Write a commit-graph file containing all reachable commits.\n +\n ------------------------------------------------\n $ git show-ref -s | git commit-graph write --stdin-commits\n ------------------------------------------------\n \n -* Write a graph file containing all commits in the current\n -- commit-graph file along with those reachable from `HEAD`.\n -+* Write a commit graph file containing all commits in the current\n -+ commit graph file along with those reachable from `HEAD`.\n ++* Write a commit-graph file containing all commits in the current\n + commit-graph file along with those reachable from `HEAD`.\n +\n ------------------------------------------------\n - $ git rev-parse HEAD | git commit-graph write --stdin-commits --append\n4: fc81147ea4 < -: ---------- git-commit-graph.txt: refer to the \"commit graph file\" without dash\n-: ---------- > 4: 99b64287ec Doc: refer to the \"commit-graph file\" with dash\n-- \n2.19.0.216.g2d3b1c576c\n\n"},{"id":"359094","messageId":"837ef2f231b078cbb0eff3b33917fcc38626d788.1538075326.git.martin.agren@gmail.com","threadId":"49383","inReplyTo":"cover.1538075326.git.martin.agren@gmail.com","subject":"[PATCH v2 1/4] git-commit-graph.txt: fix bullet lists","fromName":"Martin Ågren","fromEmail":"martin.agren@gmail.com","sentAt":"2018-09-27T19:12:19Z","receivedAt":"2018-09-27T19:12:45Z","isPatch":true,"sender":{"key":"martin.agren@gmail.com","avatar":null},"body":"We have a couple of bullet items which span multiple lines, and where we\nhave prefixed each line with a `*`. (This might be the result of a text\neditor trying to help.) This results in each line being typeset as a\nseparate bullet item. Drop the extra `*`.\n\nSigned-off-by: Martin Ågren \n---\n Documentation/git-commit-graph.txt | 4 ++--\n 1 file changed, 2 insertions(+), 2 deletions(-)\n\ndiff --git a/Documentation/git-commit-graph.txt b/Documentation/git-commit-graph.txt\nindex dececb79d7..f42f2a1481 100644\n--- a/Documentation/git-commit-graph.txt\n+++ b/Documentation/git-commit-graph.txt\n@@ -73,7 +73,7 @@ $ git commit-graph write\n ------------------------------------------------\n \n * Write a graph file, extending the current graph file using commits\n-* in .\n+ in .\n +\n ------------------------------------------------\n $ echo | git commit-graph write --stdin-packs\n@@ -86,7 +86,7 @@ $ git show-ref -s | git commit-graph write --stdin-commits\n ------------------------------------------------\n \n * Write a graph file containing all commits in the current\n-* commit-graph file along with those reachable from HEAD.\n+ commit-graph file along with those reachable from HEAD.\n +\n ------------------------------------------------\n $ git rev-parse HEAD | git commit-graph write --stdin-commits --append\n-- \n2.19.0.216.g2d3b1c576c\n\n"},{"id":"359095","messageId":"759bc886d84e3b38d48e3fce7956a517f9055462.1538075326.git.martin.agren@gmail.com","threadId":"49383","inReplyTo":"cover.1538075326.git.martin.agren@gmail.com","subject":"[PATCH v2 3/4] git-commit-graph.txt: refer to \"*commit*-graph file\"","fromName":"Martin Ågren","fromEmail":"martin.agren@gmail.com","sentAt":"2018-09-27T19:12:21Z","receivedAt":"2018-09-27T19:12:48Z","isPatch":true,"sender":{"key":"martin.agren@gmail.com","avatar":null},"body":"This document sometimes refers to the \"commit-graph file\" as just \"the\ngraph file\". This saves a couple of words here and there at the risk of\nconfusion. In particular, the documentation for `git commit-graph read`\nappears to suggest that there are indeed different types of graph files.\n\nLet's just write out the full name everywhere.\n\nThe full name, by the way, is not the dash-less \"commit graph file\".\nUse the dashed form. (The next commit will fix the remaining few\ninstances of the \"commit graph file\" in this document.)\n\nSigned-off-by: Martin Ågren \n---\n Documentation/git-commit-graph.txt | 12 ++++++------\n 1 file changed, 6 insertions(+), 6 deletions(-)\n\ndiff --git a/Documentation/git-commit-graph.txt b/Documentation/git-commit-graph.txt\nindex 6ac610f016..f33330a171 100644\n--- a/Documentation/git-commit-graph.txt\n+++ b/Documentation/git-commit-graph.txt\n@@ -54,8 +54,8 @@ existing commit-graph file.\n \n 'read'::\n \n-Read a graph file given by the commit-graph file and output basic\n-details about the graph file. Used for debugging purposes.\n+Read the commit-graph file and output basic details about it.\n+Used for debugging purposes.\n \n 'verify'::\n \n@@ -73,20 +73,20 @@ EXAMPLES\n $ git commit-graph write\n ------------------------------------------------\n \n-* Write a graph file, extending the current graph file using commits\n- in ``.\n+* Write a commit-graph file, extending the current commit-graph file\n+ using commits in ``.\n +\n ------------------------------------------------\n $ echo | git commit-graph write --stdin-packs\n ------------------------------------------------\n \n-* Write a graph file containing all reachable commits.\n+* Write a commit-graph file containing all reachable commits.\n +\n ------------------------------------------------\n $ git show-ref -s | git commit-graph write --stdin-commits\n ------------------------------------------------\n \n-* Write a graph file containing all commits in the current\n+* Write a commit-graph file containing all commits in the current\n commit-graph file along with those reachable from `HEAD`.\n +\n ------------------------------------------------\n-- \n2.19.0.216.g2d3b1c576c\n\n"},{"id":"359096","messageId":"9759a162ca95c3ff9478f0947da3bed9e0493dac.1538075326.git.martin.agren@gmail.com","threadId":"49383","inReplyTo":"cover.1538075326.git.martin.agren@gmail.com","subject":"[PATCH v2 2/4] git-commit-graph.txt: typeset more in monospace","fromName":"Martin Ågren","fromEmail":"martin.agren@gmail.com","sentAt":"2018-09-27T19:12:20Z","receivedAt":"2018-09-27T19:12:49Z","isPatch":true,"sender":{"key":"martin.agren@gmail.com","avatar":null},"body":"While we're here, fix an instance of \"folder\" to be \"directory\".\n\nSigned-off-by: Martin Ågren \n---\n Documentation/git-commit-graph.txt | 13 +++++++------\n 1 file changed, 7 insertions(+), 6 deletions(-)\n\ndiff --git a/Documentation/git-commit-graph.txt b/Documentation/git-commit-graph.txt\nindex f42f2a1481..6ac610f016 100644\n--- a/Documentation/git-commit-graph.txt\n+++ b/Documentation/git-commit-graph.txt\n@@ -25,9 +25,9 @@ OPTIONS\n --object-dir::\n \tUse given directory for the location of packfiles and commit graph\n \tfile. This parameter exists to specify the location of an alternate\n-\tthat only has the objects directory, not a full .git directory. The\n-\tcommit graph file is expected to be at /info/commit-graph and\n-\tthe packfiles are expected to be in /pack.\n+\tthat only has the objects directory, not a full `.git` directory. The\n+\tcommit graph file is expected to be at `/info/commit-graph` and\n+\tthe packfiles are expected to be in `/pack`.\n \n \n COMMANDS\n@@ -66,14 +66,15 @@ database. Used to check for corrupted data.\n EXAMPLES\n --------\n \n-* Write a commit graph file for the packed commits in your local .git folder.\n+* Write a commit graph file for the packed commits in your local `.git`\n+ directory.\n +\n ------------------------------------------------\n $ git commit-graph write\n ------------------------------------------------\n \n * Write a graph file, extending the current graph file using commits\n- in .\n+ in ``.\n +\n ------------------------------------------------\n $ echo | git commit-graph write --stdin-packs\n@@ -86,7 +87,7 @@ $ git show-ref -s | git commit-graph write --stdin-commits\n ------------------------------------------------\n \n * Write a graph file containing all commits in the current\n- commit-graph file along with those reachable from HEAD.\n+ commit-graph file along with those reachable from `HEAD`.\n +\n ------------------------------------------------\n $ git rev-parse HEAD | git commit-graph write --stdin-commits --append\n-- \n2.19.0.216.g2d3b1c576c\n\n"},{"id":"359097","messageId":"99b64287ec22e8690d5518002240be3e9147cb8e.1538075326.git.martin.agren@gmail.com","threadId":"49383","inReplyTo":"cover.1538075326.git.martin.agren@gmail.com","subject":"[PATCH v2 4/4] Doc: refer to the \"commit-graph file\" with dash","fromName":"Martin Ågren","fromEmail":"martin.agren@gmail.com","sentAt":"2018-09-27T19:12:22Z","receivedAt":"2018-09-27T19:12:51Z","isPatch":true,"sender":{"key":"martin.agren@gmail.com","avatar":null},"body":"The file processed by `git commit-graph` is referred to as the\n\"commit-graph file\", also with a dash. We have a few references to the\n\"commit graph file\", though, without the dash. These occur in\ngit-commit-graph.txt as well as in Doc/technical/commit-graph.txt. Fix\nthem.\n\nDo not change the references to the \"commit graph\" (without \"... file\")\nas a data structure.\n\nSigned-off-by: Martin Ågren \n---\n Documentation/git-commit-graph.txt | 12 ++++++------\n Documentation/technical/commit-graph.txt | 8 ++++----\n 2 files changed, 10 insertions(+), 10 deletions(-)\n\ndiff --git a/Documentation/git-commit-graph.txt b/Documentation/git-commit-graph.txt\nindex f33330a171..624470e198 100644\n--- a/Documentation/git-commit-graph.txt\n+++ b/Documentation/git-commit-graph.txt\n@@ -3,7 +3,7 @@ git-commit-graph(1)\n \n NAME\n ----\n-git-commit-graph - Write and verify Git commit graph files\n+git-commit-graph - Write and verify Git commit-graph files\n \n \n SYNOPSIS\n@@ -17,16 +17,16 @@ SYNOPSIS\n DESCRIPTION\n -----------\n \n-Manage the serialized commit graph file.\n+Manage the serialized commit-graph file.\n \n \n OPTIONS\n -------\n --object-dir::\n-\tUse given directory for the location of packfiles and commit graph\n+\tUse given directory for the location of packfiles and commit-graph\n \tfile. This parameter exists to specify the location of an alternate\n \tthat only has the objects directory, not a full `.git` directory. The\n-\tcommit graph file is expected to be at `/info/commit-graph` and\n+\tcommit-graph file is expected to be at `/info/commit-graph` and\n \tthe packfiles are expected to be in `/pack`.\n \n \n@@ -34,7 +34,7 @@ COMMANDS\n --------\n 'write'::\n \n-Write a commit graph file based on the commits found in packfiles.\n+Write a commit-graph file based on the commits found in packfiles.\n +\n With the `--stdin-packs` option, generate the new commit graph by\n walking objects only in the specified pack-indexes. (Cannot be combined\n@@ -66,7 +66,7 @@ database. Used to check for corrupted data.\n EXAMPLES\n --------\n \n-* Write a commit graph file for the packed commits in your local `.git`\n+* Write a commit-graph file for the packed commits in your local `.git`\n directory.\n +\n ------------------------------------------------\ndiff --git a/Documentation/technical/commit-graph.txt b/Documentation/technical/commit-graph.txt\nindex c664acbd76..6b7dde011e 100644\n--- a/Documentation/technical/commit-graph.txt\n+++ b/Documentation/technical/commit-graph.txt\n@@ -15,13 +15,13 @@ There are two main costs here:\n 1. Decompressing and parsing commits.\n 2. Walking the entire graph to satisfy topological order constraints.\n \n-The commit graph file is a supplemental data structure that accelerates\n+The commit-graph file is a supplemental data structure that accelerates\n commit graph walks. If a user downgrades or disables the 'core.commitGraph'\n config setting, then the existing ODB is sufficient. The file is stored\n as \"commit-graph\" either in the .git/objects/info directory or in the info\n directory of an alternate.\n \n-The commit graph file stores the commit graph structure along with some\n+The commit-graph file stores the commit graph structure along with some\n extra metadata to speed up graph walks. By listing commit OIDs in lexi-\n cographic order, we can identify an integer position for each commit and\n refer to the parents of a commit using those integer positions. We use\n@@ -103,7 +103,7 @@ that of a parent.\n Design Details\n --------------\n \n-- The commit graph file is stored in a file named 'commit-graph' in the\n+- The commit-graph file is stored in a file named 'commit-graph' in the\n .git/objects/info directory. This could be stored in the info directory\n of an alternate.\n \n@@ -127,7 +127,7 @@ Future Work\n - 'log --topo-order'\n - 'tag --merged'\n \n-- A server could provide a commit graph file as part of the network protocol\n+- A server could provide a commit-graph file as part of the network protocol\n to avoid extra calculations by clients. This feature is only of benefit if\n the user is willing to trust the file, because verifying the file is correct\n is as hard as computing it from scratch.\n-- \n2.19.0.216.g2d3b1c576c\n\n"},{"id":"359098","messageId":"31d467b9-1ffd-5c1d-2ff2-f4cb76854f0a@gmail.com","threadId":"49383","inReplyTo":"cover.1538075326.git.martin.agren@gmail.com","subject":"Re: [PATCH v2 0/4] git-commit-graph.txt: various cleanups","fromName":"Derrick Stolee","fromEmail":"stolee@gmail.com","sentAt":"2018-09-27T19:16:43Z","receivedAt":"2018-09-27T19:16:46Z","isPatch":true,"sender":{"key":"stolee@gmail.com","avatar":"https://avatars.githubusercontent.com/u/570044?v=4"},"body":"On 9/27/2018 3:12 PM, Martin Ågren wrote:\n> This v2 starts with the same two patches as v1 did, then goes on to\n> change \"[commit] graph file\" to \"commit-graph file\" with a dash, to\n> match other instances as well as Derrick's feedback.\nThanks! This version satisfies my concerns and looks good to me.\n\nReviewed-by: Derrick Stolee \n"},{"id":"359099","messageId":"CAN0heSpih+eMrbar29q6g7-aHD8SmufZvDTe97Me2hF6CJb3Qg@mail.gmail.com","threadId":"49383","inReplyTo":"31d467b9-1ffd-5c1d-2ff2-f4cb76854f0a@gmail.com","subject":"Re: [PATCH v2 0/4] git-commit-graph.txt: various cleanups","fromName":"Martin Ågren","fromEmail":"martin.agren@gmail.com","sentAt":"2018-09-27T19:21:31Z","receivedAt":"2018-09-27T19:21:45Z","isPatch":true,"sender":{"key":"martin.agren@gmail.com","avatar":null},"body":"Hi Derrick\n\nOn Thu, 27 Sep 2018 at 21:16, Derrick Stolee wrote:\n> Thanks! This version satisfies my concerns and looks good to me.\n>\n> Reviewed-by: Derrick Stolee \n\nThanks for the spectacularly snappy review. I don't expect commit graphs\nto help my use cases a lot, but I still wanted to try them out a little\nand stumbled on the `*` lists. Thanks for doing this work!\n\nMartin\n"}]}