All of lore.kernel.org
 help / color / mirror / Atom feed
From: Todd Zullinger <tmz@pobox.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: git@vger.kernel.org, Jeff Hostetler <jeffhost@microsoft.com>
Subject: Re: [PATCH] doc: replace "--" with {litdd} in credential-cache/fsmonitor
Date: Thu, 7 Apr 2022 14:05:29 -0400	[thread overview]
Message-ID: <Yk8n6R33HrCCvSsP@pobox.com> (raw)
In-Reply-To: <nycvar.QRO.7.76.6.2204071528590.347@tvgsbejvaqbjf.bet>

Hi Johannes,

Johannes Schindelin wrote:
> Hi Todd,
>> diff --git a/Documentation/config/core.txt b/Documentation/config/core.txt
>> index 889522956e..e67392cc83 100644
>> --- a/Documentation/config/core.txt
>> +++ b/Documentation/config/core.txt
>> @@ -63,7 +63,7 @@ core.protectNTFS::
>>
>>  core.fsmonitor::
>>  	If set to true, enable the built-in file system monitor
>> -	daemon for this working directory (linkgit:git-fsmonitor--daemon[1]).
>> +	daemon for this working directory (linkgit:git-fsmonitor{litdd}daemon[1]).
> 
> I am not quite certain that using `{litdd}` in a `linkgit` construct works
> both in AsciiDoc and AsciiDoctor, but I trust that you have verified that
> this works.

I did not do a build with asciidoc, but when I still built
the Fedora packages with asciidoc, we had already fixed
similar issues with `{litdd}` and I don't believe that has
changed.  If it has, then we've got other broken links:

    $ git grep 'linkgit:[^]]+\{litdd\}[^]]*\[' -- Documentation/ | wc -l
    8

    $ git grep 'linkgit:[^]]+--[^]]*\[' -- Documentation/ | wc -l
    0

> Thank you for doing this,

And thank you for reviewing and testing.

-- 
Todd

  reply	other threads:[~2022-04-07 18:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-06 18:41 [PATCH] doc: replace "--" with {litdd} in credential-cache/fsmonitor Todd Zullinger
2022-04-07 13:33 ` Johannes Schindelin
2022-04-07 18:05   ` Todd Zullinger [this message]
2022-04-07 17:23 ` Ævar Arnfjörð Bjarmason
2022-04-07 18:15   ` Todd Zullinger
2022-04-07 18:35     ` Ævar Arnfjörð Bjarmason

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=Yk8n6R33HrCCvSsP@pobox.com \
    --to=tmz@pobox.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=jeffhost@microsoft.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.