{"thread":{"id":"10566","subject":"[PATCH] Include diff options in the git-log manpage","startedAt":"2007-11-01T14:57:39Z","lastAt":"2007-12-05T06:45:08Z","messageCount":8,"participants":["Miklos Vajna","Johannes Schindelin","Junio C Hamano"],"isPatch":true,"patchVersion":1,"patchTotal":null},"messages":[{"id":"57834","messageId":"1193929060-6183-1-git-send-email-vmiklos@frugalware.org","threadId":"10566","inReplyTo":null,"subject":"[PATCH] Document that using -M without other diff options is not a good idea","fromName":"Miklos Vajna","fromEmail":"vmiklos@frugalware.org","sentAt":"2007-11-01T14:57:39Z","receivedAt":"2007-11-01T14:57:39Z","isPatch":true,"sender":{"key":"vmiklos@frugalware.org","avatar":"https://gravatar.com/avatar/401c1cbbb3a5d13e650c691a2c71d6fd0b80df1a01bc74d9f1972675dd58f2bd?d=mp&s=160"},"body":"Signed-off-by: Miklos Vajna \n---\n\nI just noticed that I used 'git log -M' in some scripts which is obviously bad.\nPeople should not use that option without other diff options.\n\n Documentation/diff-options.txt | 4 +++-\n 1 files changed, 3 insertions(+), 1 deletions(-)\n\ndiff --git a/Documentation/diff-options.txt b/Documentation/diff-options.txt\nindex b1f528a..ed827f8 100644\n--- a/Documentation/diff-options.txt\n+++ b/Documentation/diff-options.txt\n@@ -92,7 +92,9 @@\n \tBreak complete rewrite changes into pairs of delete and create.\n \n -M::\n-\tDetect renames.\n+\tDetect renames. It's no good using this option if you don't use diff\n+\toptions like `--name-status`, `-p` or `--stat` as it will just slow\n+\tdown the revision walker.\n \n -C::\n \tDetect copies as well as renames. See also `--find-copies-harder`.\n-- \n1.5.3.5\n"},{"id":"57833","messageId":"1193929060-6183-2-git-send-email-vmiklos@frugalware.org","threadId":"10566","inReplyTo":"1193929060-6183-1-git-send-email-vmiklos@frugalware.org","subject":"[PATCH] Include diff options in the git-log manpage","fromName":"Miklos Vajna","fromEmail":"vmiklos@frugalware.org","sentAt":"2007-11-01T14:57:40Z","receivedAt":"2007-11-01T14:57:40Z","isPatch":true,"sender":{"key":"vmiklos@frugalware.org","avatar":"https://gravatar.com/avatar/401c1cbbb3a5d13e650c691a2c71d6fd0b80df1a01bc74d9f1972675dd58f2bd?d=mp&s=160"},"body":"Signed-off-by: Miklos Vajna \n---\n\nRecently I wanted to see what git log -M does but actually I was not able to\nfind it in the manpage, finally figured out that all the diff options are\nmissing from here.\n\nRemoving -p as it's already in diff-options.txt.\n\nIf this patch OK, then I would like to send a similar patch to\ngit-rev-list.txt, too.\n\n Documentation/git-log.txt | 5 ++---\n 1 files changed, 2 insertions(+), 3 deletions(-)\n\ndiff --git a/Documentation/git-log.txt b/Documentation/git-log.txt\nindex 5ec547c..4b1b982 100644\n--- a/Documentation/git-log.txt\n+++ b/Documentation/git-log.txt\n@@ -27,6 +27,8 @@ OPTIONS\n \n include::pretty-options.txt[]\n \n+include::diff-options.txt[]\n+\n -::\n \tLimits the number of commits to show.\n \n@@ -43,9 +45,6 @@ include::pretty-options.txt[]\n \tcommit. This option gives a better overview of the\n \tevolution of a particular branch.\n \n--p::\n-\tShow the change the commit introduces in a patch form.\n-\n -g, \\--walk-reflogs::\n \tShow commits as they were recorded in the reflog. The log contains\n \ta record about how the tip of a reference was changed.\n-- \n1.5.3.5\n"},{"id":"57836","messageId":"Pine.LNX.4.64.0711011508490.4362@racer.site","threadId":"10566","inReplyTo":"1193929060-6183-1-git-send-email-vmiklos@frugalware.org","subject":"Re: [PATCH] Document that using -M without other diff options is not a good idea","fromName":"Johannes Schindelin","fromEmail":"johannes.schindelin@gmx.de","sentAt":"2007-11-01T15:09:25Z","receivedAt":"2007-11-01T15:09:25Z","isPatch":true,"sender":{"key":"johannes.schindelin@gmx.de","avatar":"https://avatars.githubusercontent.com/u/127790?v=4"},"body":"Hi,\n\nOn Thu, 1 Nov 2007, Miklos Vajna wrote:\n\n> Signed-off-by: Miklos Vajna \n> ---\n> \n> I just noticed that I used 'git log -M' in some scripts which is obviously bad.\n> People should not use that option without other diff options.\n> \n> Documentation/diff-options.txt | 4 +++-\n> 1 files changed, 3 insertions(+), 1 deletions(-)\n> \n> diff --git a/Documentation/diff-options.txt b/Documentation/diff-options.txt\n> index b1f528a..ed827f8 100644\n> --- a/Documentation/diff-options.txt\n> +++ b/Documentation/diff-options.txt\n> @@ -92,7 +92,9 @@\n> \tBreak complete rewrite changes into pairs of delete and create.\n> \n> -M::\n> -\tDetect renames.\n> +\tDetect renames. It's no good using this option if you don't use diff\n> +\toptions like `--name-status`, `-p` or `--stat` as it will just slow\n> +\tdown the revision walker.\n\nAs I remarked on IRC earlier, this will also show up in the man page of \ngit-diff, too. Rather funny, no?\n\nCiao,\nDscho\n"},{"id":"57838","messageId":"20071101152451.GI27987@genesis.frugalware.org","threadId":"10566","inReplyTo":"Pine.LNX.4.64.0711011508490.4362@racer.site","subject":"Re: [PATCH] Document that using -M without other diff options is not a good idea","fromName":"Miklos Vajna","fromEmail":"vmiklos@frugalware.org","sentAt":"2007-11-01T15:24:51Z","receivedAt":"2007-11-01T15:24:51Z","isPatch":true,"sender":{"key":"vmiklos@frugalware.org","avatar":"https://gravatar.com/avatar/401c1cbbb3a5d13e650c691a2c71d6fd0b80df1a01bc74d9f1972675dd58f2bd?d=mp&s=160"},"body":"On Thu, Nov 01, 2007 at 03:09:25PM +0000, Johannes Schindelin wrote:\n> As I remarked on IRC earlier, this will also show up in the man page of \n> git-diff, too. Rather funny, no?\n\nah, then i misunderstood you. so the correct way would be to juse ignore\nthe -M switch if it's useless? my problem is that if you use git log -M\nthen it's a pointless slowdown and you can't find this in the doc :s\n\nthanks,\n- VMiklos\n"},{"id":"59503","messageId":"20071112153717.GI5309@genesis.frugalware.org","threadId":"10566","inReplyTo":"1193929060-6183-2-git-send-email-vmiklos@frugalware.org","subject":"Re: [PATCH] Include diff options in the git-log manpage","fromName":"Miklos Vajna","fromEmail":"vmiklos@frugalware.org","sentAt":"2007-11-12T15:37:17Z","receivedAt":"2007-11-12T15:37:17Z","isPatch":true,"sender":{"key":"vmiklos@frugalware.org","avatar":"https://gravatar.com/avatar/401c1cbbb3a5d13e650c691a2c71d6fd0b80df1a01bc74d9f1972675dd58f2bd?d=mp&s=160"},"body":"On Thu, Nov 01, 2007 at 03:57:40PM +0100, Miklos Vajna wrote:\n> Signed-off-by: Miklos Vajna \n> ---\n> \n> Recently I wanted to see what git log -M does but actually I was not able to\n> find it in the manpage, finally figured out that all the diff options are\n> missing from here.\n> \n> Removing -p as it's already in diff-options.txt.\n> \n> If this patch OK, then I would like to send a similar patch to\n> git-rev-list.txt, too.\n> \n> Documentation/git-log.txt | 5 ++---\n> 1 files changed, 2 insertions(+), 3 deletions(-)\n\ncould somebody please comment this patch? does it look ok?\n\nthanks,\n- VMiklos\n"},{"id":"61903","messageId":"20071204122859.GQ31750@genesis.frugalware.org","threadId":"10566","inReplyTo":"1193929060-6183-2-git-send-email-vmiklos@frugalware.org","subject":"Re: [PATCH] Include diff options in the git-log manpage","fromName":"Miklos Vajna","fromEmail":"vmiklos@frugalware.org","sentAt":"2007-12-04T12:28:59Z","receivedAt":"2007-12-04T12:28:59Z","isPatch":true,"sender":{"key":"vmiklos@frugalware.org","avatar":"https://gravatar.com/avatar/401c1cbbb3a5d13e650c691a2c71d6fd0b80df1a01bc74d9f1972675dd58f2bd?d=mp&s=160"},"body":"On Thu, Nov 01, 2007 at 03:57:40PM +0100, Miklos Vajna wrote:\n> Recently I wanted to see what git log -M does but actually I was not able to\n> find it in the manpage, finally figured out that all the diff options are\n> missing from here.\n> \n> Removing -p as it's already in diff-options.txt.\n\ncould you please have a look at this patch? this also fixes the \"-C is\nmissing from man git-log\" issue which was reported on IRC today.\n\nthanks,\n- VMiklos\n"},{"id":"61931","messageId":"7vzlwq4a1w.fsf@gitster.siamese.dyndns.org","threadId":"10566","inReplyTo":"20071204122859.GQ31750@genesis.frugalware.org","subject":"Re: [PATCH] Include diff options in the git-log manpage","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2007-12-04T17:57:47Z","receivedAt":"2007-12-04T17:57:47Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Miklos Vajna writes:\n\n> On Thu, Nov 01, 2007 at 03:57:40PM +0100, Miklos Vajna wrote:\n>> Recently I wanted to see what git log -M does but actually I was not able to\n>> find it in the manpage, finally figured out that all the diff options are\n>> missing from here.\n>> \n>> Removing -p as it's already in diff-options.txt.\n>\n> could you please have a look at this patch? this also fixes the \"-C is\n> missing from man git-log\" issue which was reported on IRC today.\n\nThere was a patch around diff options documentation from Sergei\nlast month, and somehow I thought it covered this issue as well.\n\nWill format the docs before and after your fix, compare them, and then\ndecide either to drop or accept, which will take some time but will be\ndone before -rc0.\n\nThanks.\n"},{"id":"61969","messageId":"7vve7d1vyj.fsf@gitster.siamese.dyndns.org","threadId":"10566","inReplyTo":"20071204122859.GQ31750@genesis.frugalware.org","subject":"Re: [PATCH] Include diff options in the git-log manpage","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2007-12-05T06:45:08Z","receivedAt":"2007-12-05T06:45:08Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Miklos Vajna writes:\n\n> On Thu, Nov 01, 2007 at 03:57:40PM +0100, Miklos Vajna wrote:\n>> Recently I wanted to see what git log -M does but actually I was not able to\n>> find it in the manpage, finally figured out that all the diff options are\n>> missing from here.\n>> \n>> Removing -p as it's already in diff-options.txt.\n>\n> could you please have a look at this patch? this also fixes the \"-C is\n> missing from man git-log\" issue which was reported on IRC today.\n\nHave you proofread the whole output after your patch?\n\n * It makes it say \"--raw ... this is the default\", while for \"git log\"\n no diff output is the default.\n\n * Also it says \"-p ... (see section on generating patches)\"; there is\n no such section.\n\nThis can be a possible fixup on top of your patch. It has potential to\naffect other documentation pages that includes the files touched. I\nhave formatted log, diff and format-patch before your patch and after\nyour patch plus this patch, and eyeballed the difference, but please\ndouble check.\n\n---\n\n Documentation/diff-format.txt | 159 +--------------------------------\n Documentation/diff-generate-patch.txt | 161 +++++++++++++++++++++++++++++++++\n Documentation/diff-options.txt | 2 +\n Documentation/git-log.txt | 2 +\n 4 files changed, 166 insertions(+), 158 deletions(-)\n\ndiff --git a/Documentation/diff-format.txt b/Documentation/diff-format.txt\nindex 9709c35..2c3a4c4 100644\n--- a/Documentation/diff-format.txt\n+++ b/Documentation/diff-format.txt\n@@ -83,161 +83,4 @@ Note that 'combined diff' lists only files which were modified from\n all parents.\n \n \n-Generating patches with -p\n---------------------------\n-\n-When \"git-diff-index\", \"git-diff-tree\", or \"git-diff-files\" are run\n-with a '-p' option, or \"git diff\" without the '--raw' option, they\n-do not produce the output described above; instead they produce a\n-patch file. You can customize the creation of such patches via the\n-GIT_EXTERNAL_DIFF and the GIT_DIFF_OPTS environment variables.\n-\n-What the -p option produces is slightly different from the traditional\n-diff format.\n-\n-1. It is preceded with a \"git diff\" header, that looks like\n- this:\n-\n- diff --git a/file1 b/file2\n-+\n-The `a/` and `b/` filenames are the same unless rename/copy is\n-involved. Especially, even for a creation or a deletion,\n-`/dev/null` is _not_ used in place of `a/` or `b/` filenames.\n-+\n-When rename/copy is involved, `file1` and `file2` show the\n-name of the source file of the rename/copy and the name of\n-the file that rename/copy produces, respectively.\n-\n-2. It is followed by one or more extended header lines:\n-\n- old mode \n- new mode \n- deleted file mode \n- new file mode \n- copy from \n- copy to \n- rename from \n- rename to \n- similarity index \n- dissimilarity index \n- index .. \n-\n-3. TAB, LF, double quote and backslash characters in pathnames\n- are represented as `\\t`, `\\n`, `\\\"` and `\\\\`, respectively.\n- If there is need for such substitution then the whole\n- pathname is put in double quotes.\n-\n-The similarity index is the percentage of unchanged lines, and\n-the dissimilarity index is the percentage of changed lines. It\n-is a rounded down integer, followed by a percent sign. The\n-similarity index value of 100% is thus reserved for two equal\n-files, while 100% dissimilarity means that no line from the old\n-file made it into the new one.\n-\n-\n-combined diff format\n---------------------\n-\n-\"git-diff-tree\", \"git-diff-files\" and \"git-diff\" can take '-c' or\n-'--cc' option to produce 'combined diff', which looks like this:\n-\n-------------\n-diff --combined describe.c\n-index fabadb8,cc95eb0..4866510\n---- a/describe.c\n-+++ b/describe.c\n-@@@ -98,20 -98,12 +98,20 @@@\n-\treturn (a_date > b_date) ? -1 : (a_date == b_date) ? 0 : 1;\n- }\n-\n-- static void describe(char *arg)\n- -static void describe(struct commit *cmit, int last_one)\n-++static void describe(char *arg, int last_one)\n- {\n- +\tunsigned char sha1[20];\n- +\tstruct commit *cmit;\n-\tstruct commit_list *list;\n-\tstatic int initialized = 0;\n-\tstruct commit_name *n;\n-\n- +\tif (get_sha1(arg, sha1) < 0)\n- +\t\tusage(describe_usage);\n- +\tcmit = lookup_commit_reference(sha1);\n- +\tif (!cmit)\n- +\t\tusage(describe_usage);\n- +\n-\tif (!initialized) {\n-\t\tinitialized = 1;\n-\t\tfor_each_ref(get_name);\n-------------\n-\n-1. It is preceded with a \"git diff\" header, that looks like\n- this (when '-c' option is used):\n-\n- diff --combined file\n-+\n-or like this (when '--cc' option is used):\n-\n- diff --c file\n-\n-2. It is followed by one or more extended header lines\n- (this example shows a merge with two parents):\n-\n- index ,..\n- mode ,..\n- new file mode \n- deleted file mode ,\n-+\n-The `mode ,..` line appears only if at least one of\n-the is different from the rest. Extended headers with\n-information about detected contents movement (renames and\n-copying detection) are designed to work with diff of two\n- and are not used by combined diff format.\n-\n-3. It is followed by two-line from-file/to-file header\n-\n- --- a/file\n- +++ b/file\n-+\n-Similar to two-line header for traditional 'unified' diff\n-format, `/dev/null` is used to signal created or deleted\n-files.\n-\n-4. Chunk header format is modified to prevent people from\n- accidentally feeding it to `patch -p1`. Combined diff format\n- was created for review of merge commit changes, and was not\n- meant for apply. The change is similar to the change in the\n- extended 'index' header:\n-\n- @@@ @@@\n-+\n-There are (number of parents + 1) `@` characters in the chunk\n-header for combined diff format.\n-\n-Unlike the traditional 'unified' diff format, which shows two\n-files A and B with a single column that has `-` (minus --\n-appears in A but removed in B), `+` (plus -- missing in A but\n-added to B), or `\" \"` (space -- unchanged) prefix, this format\n-compares two or more files file1, file2,... with one file X, and\n-shows how X differs from each of fileN. One column for each of\n-fileN is prepended to the output line to note how X's line is\n-different from it.\n-\n-A `-` character in the column N means that the line appears in\n-fileN but it does not appear in the result. A `+` character\n-in the column N means that the line appears in the last file,\n-and fileN does not have that line (in other words, the line was\n-added, from the point of view of that parent).\n-\n-In the above example output, the function signature was changed\n-from both files (hence two `-` removals from both file1 and\n-file2, plus `++` to mean one line that was added does not appear\n-in either file1 nor file2). Also two other lines are the same\n-from file1 but do not appear in file2 (hence prefixed with ` +`).\n-\n-When shown by `git diff-tree -c`, it compares the parents of a\n-merge commit with the merge result (i.e. file1..fileN are the\n-parents). When shown by `git diff-files -c`, it compares the\n-two unresolved merge parents with the working tree file\n-(i.e. file1 is stage 2 aka \"our version\", file2 is stage 3 aka\n-\"their version\").\n+include::diff-generate-patch.txt[]\ndiff --git a/Documentation/diff-generate-patch.txt b/Documentation/diff-generate-patch.txt\nnew file mode 100644\nindex 0000000..029c5f2\n--- /dev/null\n+++ b/Documentation/diff-generate-patch.txt\n@@ -0,0 +1,161 @@\n+Generating patches with -p\n+--------------------------\n+\n+When \"git-diff-index\", \"git-diff-tree\", or \"git-diff-files\" are run\n+with a '-p' option, \"git diff\" without the '--raw' option, or\n+\"git log\" with the \"-p\" option, they\n+do not produce the output described above; instead they produce a\n+patch file. You can customize the creation of such patches via the\n+GIT_EXTERNAL_DIFF and the GIT_DIFF_OPTS environment variables.\n+\n+What the -p option produces is slightly different from the traditional\n+diff format.\n+\n+1. It is preceded with a \"git diff\" header, that looks like\n+ this:\n+\n+ diff --git a/file1 b/file2\n++\n+The `a/` and `b/` filenames are the same unless rename/copy is\n+involved. Especially, even for a creation or a deletion,\n+`/dev/null` is _not_ used in place of `a/` or `b/` filenames.\n++\n+When rename/copy is involved, `file1` and `file2` show the\n+name of the source file of the rename/copy and the name of\n+the file that rename/copy produces, respectively.\n+\n+2. It is followed by one or more extended header lines:\n+\n+ old mode \n+ new mode \n+ deleted file mode \n+ new file mode \n+ copy from \n+ copy to \n+ rename from \n+ rename to \n+ similarity index \n+ dissimilarity index \n+ index .. \n+\n+3. TAB, LF, double quote and backslash characters in pathnames\n+ are represented as `\\t`, `\\n`, `\\\"` and `\\\\`, respectively.\n+ If there is need for such substitution then the whole\n+ pathname is put in double quotes.\n+\n+The similarity index is the percentage of unchanged lines, and\n+the dissimilarity index is the percentage of changed lines. It\n+is a rounded down integer, followed by a percent sign. The\n+similarity index value of 100% is thus reserved for two equal\n+files, while 100% dissimilarity means that no line from the old\n+file made it into the new one.\n+\n+\n+combined diff format\n+--------------------\n+\n+\"git-diff-tree\", \"git-diff-files\" and \"git-diff\" can take '-c' or\n+'--cc' option to produce 'combined diff'. For showing a merge commit\n+with \"git log -p\", this is the default format.\n+A 'combined diff' format looks like this:\n+\n+------------\n+diff --combined describe.c\n+index fabadb8,cc95eb0..4866510\n+--- a/describe.c\n++++ b/describe.c\n+@@@ -98,20 -98,12 +98,20 @@@\n+\treturn (a_date > b_date) ? -1 : (a_date == b_date) ? 0 : 1;\n+ }\n+\n+- static void describe(char *arg)\n+ -static void describe(struct commit *cmit, int last_one)\n+++static void describe(char *arg, int last_one)\n+ {\n+ +\tunsigned char sha1[20];\n+ +\tstruct commit *cmit;\n+\tstruct commit_list *list;\n+\tstatic int initialized = 0;\n+\tstruct commit_name *n;\n+\n+ +\tif (get_sha1(arg, sha1) < 0)\n+ +\t\tusage(describe_usage);\n+ +\tcmit = lookup_commit_reference(sha1);\n+ +\tif (!cmit)\n+ +\t\tusage(describe_usage);\n+ +\n+\tif (!initialized) {\n+\t\tinitialized = 1;\n+\t\tfor_each_ref(get_name);\n+------------\n+\n+1. It is preceded with a \"git diff\" header, that looks like\n+ this (when '-c' option is used):\n+\n+ diff --combined file\n++\n+or like this (when '--cc' option is used):\n+\n+ diff --c file\n+\n+2. It is followed by one or more extended header lines\n+ (this example shows a merge with two parents):\n+\n+ index ,..\n+ mode ,..\n+ new file mode \n+ deleted file mode ,\n++\n+The `mode ,..` line appears only if at least one of\n+the is different from the rest. Extended headers with\n+information about detected contents movement (renames and\n+copying detection) are designed to work with diff of two\n+ and are not used by combined diff format.\n+\n+3. It is followed by two-line from-file/to-file header\n+\n+ --- a/file\n+ +++ b/file\n++\n+Similar to two-line header for traditional 'unified' diff\n+format, `/dev/null` is used to signal created or deleted\n+files.\n+\n+4. Chunk header format is modified to prevent people from\n+ accidentally feeding it to `patch -p1`. Combined diff format\n+ was created for review of merge commit changes, and was not\n+ meant for apply. The change is similar to the change in the\n+ extended 'index' header:\n+\n+ @@@ @@@\n++\n+There are (number of parents + 1) `@` characters in the chunk\n+header for combined diff format.\n+\n+Unlike the traditional 'unified' diff format, which shows two\n+files A and B with a single column that has `-` (minus --\n+appears in A but removed in B), `+` (plus -- missing in A but\n+added to B), or `\" \"` (space -- unchanged) prefix, this format\n+compares two or more files file1, file2,... with one file X, and\n+shows how X differs from each of fileN. One column for each of\n+fileN is prepended to the output line to note how X's line is\n+different from it.\n+\n+A `-` character in the column N means that the line appears in\n+fileN but it does not appear in the result. A `+` character\n+in the column N means that the line appears in the last file,\n+and fileN does not have that line (in other words, the line was\n+added, from the point of view of that parent).\n+\n+In the above example output, the function signature was changed\n+from both files (hence two `-` removals from both file1 and\n+file2, plus `++` to mean one line that was added does not appear\n+in either file1 nor file2). Also two other lines are the same\n+from file1 but do not appear in file2 (hence prefixed with ` +`).\n+\n+When shown by `git diff-tree -c`, it compares the parents of a\n+merge commit with the merge result (i.e. file1..fileN are the\n+parents). When shown by `git diff-files -c`, it compares the\n+two unresolved merge parents with the working tree file\n+(i.e. file1 is stage 2 aka \"our version\", file2 is stage 3 aka\n+\"their version\").\ndiff --git a/Documentation/diff-options.txt b/Documentation/diff-options.txt\nindex e4af393..d0154bb 100644\n--- a/Documentation/diff-options.txt\n+++ b/Documentation/diff-options.txt\n@@ -6,7 +6,9 @@\n \n ifndef::git-format-patch[]\n ifndef::git-diff[]\n+ifndef::git-log[]\n :git-diff-core: 1\n+endif::git-log[]\n endif::git-diff[]\n endif::git-format-patch[]\n \ndiff --git a/Documentation/git-log.txt b/Documentation/git-log.txt\nindex 4b1b982..5920d17 100644\n--- a/Documentation/git-log.txt\n+++ b/Documentation/git-log.txt\n@@ -27,6 +27,7 @@ OPTIONS\n \n include::pretty-options.txt[]\n \n+:git-log: 1\n include::diff-options.txt[]\n \n -::\n@@ -77,6 +78,7 @@ include::diff-options.txt[]\n \n include::pretty-formats.txt[]\n \n+include::diff-generate-patch.txt[]\n \n Examples\n --------\n"}]}