From: "Nícolas F. R. A. Prado" <nfraprado@protonmail.com>
To: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
Cc: Jonathan Corbet <corbet@lwn.net>,
Randy Dunlap <rdunlap@infradead.org>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
lkcamp@lists.libreplanetbr.org, andrealmeid@collabora.com
Subject: Re: [RFC PATCH] docs: Warn when auto xref to document fails
Date: Sat, 13 Mar 2021 14:14:59 +0000 [thread overview]
Message-ID: <C9WA68VRXNQ4.OJ34WFAPDT1Q@notapiano> (raw)
Em 2021-02-11 16:57, Mauro Carvalho Chehab escreveu:
>
> Em Thu, 11 Feb 2021 18:10:36 +0000
> Nícolas F. R. A. Prado <nfraprado@protonmail.com> escreveu:
>
> > Print warning when automarkup fails to cross-reference to another
> > document, so that it doesn't fail silently.
> >
> > Signed-off-by: Nícolas F. R. A. Prado <nfraprado@protonmail.com>
> > ---
> >
> > This patch is marked as RFC because it causes a lot of new warnings currently.
> > So the patch should only be applied after we reduce this to zero. The warnings
> > are listed at the end.
>
> Maybe it could be enabled if W=2?
Sorry for the delay, I was waiting to see if Jon had any opinion on this.
To me it seems these are relevant warnings that sould always be printed, but I'm
not too sure.
In any case, I'll work on a v2 implementing the mapping I talked about on this
patch, and fixing the warnings I can, and if there are any left, I'll make it
only output on W=2 then.
Thanks,
Nícolas
next reply other threads:[~2021-03-13 14:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-13 14:14 Nícolas F. R. A. Prado [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-02-11 18:10 [RFC PATCH] docs: Warn when auto xref to document fails Nícolas F. R. A. Prado
2021-02-11 19:57 ` Mauro Carvalho Chehab
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=C9WA68VRXNQ4.OJ34WFAPDT1Q@notapiano \
--to=nfraprado@protonmail.com \
--cc=andrealmeid@collabora.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkcamp@lists.libreplanetbr.org \
--cc=mchehab+huawei@kernel.org \
--cc=rdunlap@infradead.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox