Re: [PATCH] Include rev-list options in git-log manpage.
From: Junio C Hamano <hidden>
Date: 2016-06-15 22:44:06
Possibly related (same subject, not in this thread)
- 2016-06-15 · [PATCH] Include rev-list options in git-log manpage. · Miklos Vajna <hidden>
- 2016-06-15 · Re: [PATCH] Include rev-list options in git-log manpage. · Junio C Hamano <hidden>
- 2016-06-15 · [PATCH] Include rev-list options in git-log manpage. · Miklos Vajna <hidden>
- 2016-06-15 · Re: [PATCH] Include rev-list options in git-log manpage. · Johannes Sixt <hidden>
- 2016-06-15 · [PATCH] Include rev-list options in git-log manpage. · Miklos Vajna <hidden>
Miklos Vajna [off-list ref] writes:
+ifndef::git-log[] Using these options, linkgit:git-rev-list[1] will act similar to the more specialized family of commit log tools: linkgit:git-log[1], linkgit:git-show[1], and linkgit:git-whatchanged[1] +endif::git-log[]
quoted hunk
+ifndef::git-log[] --bisect:: Limit output to the one commit object which is roughly halfway between@@ -388,6 +302,7 @@ may not compile for example). This option can be used along with `--bisect-vars`, in this case, after all the sorted commit objects, there will be the same text as if `--bisect-vars` had been used alone. +endif::git-log[]
I do not like these. What you are really trying to express is "this section makes sense only in rev-list documentation", not "among the current set of documentation, the one this section does not make sense in is git-log". We might end up including this in some other documents. IOW, they should rather be "ifdef::git-rev-list[]" instead, (of course you have to define that token yourself if there isn't one already).