Junio C Hamano <gitster@xxxxxxxxx> writes: > Junio C Hamano <gitster@xxxxxxxxx> writes: > >> The rendered result is bad in the same way with or without this >> patch applied, and "git clone" manual page is simply incorrect by >> mangling a handful of command line options. A recent bug report in >> the thread that contains >> >> https://lore.kernel.org/git/xmqqle1xjm1s.fsf@gitster.g/ >> >> gives us more details. > > With Jean-Noël Avila's {empty} patch applied, would this patch be > still necessary? The answer is no. I managed to reproduce the problem your patch fixes locally, applied Jean-Noël's patch which corrected the mark-up to avoid losing text in the [square brackets], but the problem still reproduced. It really seems that the `monospaced` text that are used in the SYNOPSIS section are rendered with display:block. I am not sure if forcing any <code> that appears as a (direct or indirect) descendant of <pre> with custom css is specific enough, but that certainly covers the breakage we see on the page. So the difference I observed between git-clone.html and say git-add.html is purely coming from use of `monospaced` in SYNOPSIS, and not because the unintended triggering of a feature by [text]`more text` that Jean-Noël's patch fixes. With or without that fix, the css tweak is still needed (it may be overly generic and may require us to tighten the selector later, but we can worry about it when somebody finds an actual breakage). It is unfortunate that all .html files ought to be generated in this project (in other words, nobody writes HTML by hand), but asciidoc(tor) insists that docinfo for html backend must be stored in a file whose extension is .html, which caused a "huh?" Ramsay reported earlier. Will queue. Thanks.
