From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
To: Thorsten Leemhuis <linux@leemhuis.info>
Cc: Linux Doc Mailing List <linux-doc@vger.kernel.org>,
"Alexander A. Klimov" <grandmaster@al2klimov.de>,
Jonathan Corbet <corbet@lwn.net>, Alex Shi <alexs@kernel.org>,
Federico Vaga <federico.vaga@vaga.pv.it>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Harry Wei <harryxiyou@gmail.com>, Wu XiangCheng <bobwxc@email.cn>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 17/19] docs: replace transation references for reporting-bugs.rst
Date: Wed, 7 Apr 2021 11:39:34 +0200 [thread overview]
Message-ID: <20210407113934.1a61ad9e@coco.lan> (raw)
In-Reply-To: <1c37acb4-f927-e2f7-8c77-d4fc2644f1d8@leemhuis.info>
Em Wed, 7 Apr 2021 10:52:14 +0200
Thorsten Leemhuis <linux@leemhuis.info> escreveu:
> On 07.04.21 10:20, Mauro Carvalho Chehab wrote:
> > Changeset d2ce285378b0 ("docs: make reporting-issues.rst official and delete reporting-bugs.rst")
> > dropped reporting-bugs.rst, in favor of reporting-issues.rst, but
> > translations still need to be updated, in order to point to the
> > new file.
> >
> > Fixes: d2ce285378b0 ("docs: make reporting-issues.rst official and delete reporting-bugs.rst")
> > Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
>
> Well, yeah, might be the right thing to do. But FWIW: when I recently
> submitted the change that became d2ce285378b0 I actually pointed out
> that it breaks some of the translations. Back then I considered to do
> what you did with this patch, but among others got a reply from Jonathan
> who said "let the translators catch up on their own time". For details
> see this thread:
> https://lore.kernel.org/linux-doc/87h7krksvu.fsf@meer.lwn.net/
Hmm... at the e-mail you mentioned, Jon commented that:
"None of the broken references actually generate warnings"
That's actually not the case: they do generate warnings if
the Kernel is built with CONFIG_WARN_MISSING_DOCUMENTS:
Documentation/translations/zh_CN/admin-guide/reporting-issues.rst: Documentation/admin-guide/reporting-bugs.rst
Documentation/translations/zh_CN/admin-guide/reporting-issues.rst: Documentation/admin-guide/reporting-bugs.rst
As it will call the ./scripts/documentation-file-ref-check.
That's basically why I detected and submitted a fix ;-)
Thanks,
Mauro
next prev parent reply other threads:[~2021-04-07 9:40 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-07 8:20 [PATCH v2 00/19] Fix broken documentation file references Mauro Carvalho Chehab
2021-04-07 8:20 ` [PATCH v2 01/19] MAINTAINERS: update ste,mcde.yaml reference Mauro Carvalho Chehab
2021-04-07 8:20 ` [PATCH v2 02/19] MAINTAINERS: update brcm,bcm-v3d.yaml reference Mauro Carvalho Chehab
2021-04-07 8:20 ` [PATCH v2 03/19] MAINTAINERS: update fsl,dpaa2-console.yaml reference Mauro Carvalho Chehab
2021-04-07 8:20 ` [PATCH v2 04/19] MAINTAINERS: update mtk-sd.yaml reference Mauro Carvalho Chehab
2021-04-07 8:20 ` [PATCH v2 05/19] MAINTAINERS: update snps,dw-axi-dmac.yaml reference Mauro Carvalho Chehab
2021-04-07 8:20 ` [PATCH v2 06/19] dt-bindings: don't use ../dir for doc references Mauro Carvalho Chehab
2021-04-07 8:20 ` [PATCH v2 07/19] dt-bindings: fix references for iio-bindings.txt Mauro Carvalho Chehab
2021-04-07 10:18 ` Jonathan Cameron
2021-04-07 10:39 ` Sebastian Reichel
2021-04-07 12:15 ` Guenter Roeck
2021-04-07 8:20 ` [PATCH v2 08/19] dt-bindings: iommu: mediatek: update mediatek,iommu.yaml references Mauro Carvalho Chehab
2021-04-07 8:20 ` [PATCH v2 09/19] dt-bindings: i3c: update i3c.yaml references Mauro Carvalho Chehab
2021-04-07 11:34 ` Alexandre Belloni
2021-04-07 8:20 ` [PATCH v2 10/19] dt-bindings:iio:adc: update motorola,cpcap-adc.yaml reference Mauro Carvalho Chehab
2021-04-07 10:18 ` Jonathan Cameron
2021-04-07 8:20 ` [PATCH v2 11/19] dt-bindings:iio:adc: update dlg,da9150-gpadc.yaml reference Mauro Carvalho Chehab
2021-04-07 10:19 ` Jonathan Cameron
2021-04-07 8:20 ` [PATCH v2 12/19] dt-bindings: power: supply: da9150: update da9150-charger.txt reference Mauro Carvalho Chehab
2021-04-07 19:14 ` Sebastian Reichel
2021-04-07 8:20 ` [PATCH v2 13/19] dt-bindings: power: supply: da9150: update da9150-fg.txt reference Mauro Carvalho Chehab
2021-04-07 8:20 ` [PATCH v2 14/19] docs: update sysfs-platform_profile.rst reference Mauro Carvalho Chehab
2021-04-07 8:20 ` [PATCH v2 15/19] docs: update rcu_dereference.rst reference Mauro Carvalho Chehab
2021-04-07 8:20 ` [PATCH v2 16/19] docs: vcpu-requests.rst: fix reference for atomic ops Mauro Carvalho Chehab
2021-04-07 8:20 ` [PATCH v2 17/19] docs: replace transation references for reporting-bugs.rst Mauro Carvalho Chehab
2021-04-07 8:52 ` Thorsten Leemhuis
2021-04-07 9:39 ` Mauro Carvalho Chehab [this message]
2021-04-07 12:06 ` Federico Vaga
2021-04-07 9:34 ` Wu X.C.
2021-04-07 12:00 ` Federico Vaga
2021-04-07 8:20 ` [PATCH v2 18/19] docs: translations/zh_CN: fix a typo at 8.Conclusion.rst Mauro Carvalho Chehab
2021-04-07 9:11 ` Wu X.C.
2021-04-07 8:20 ` [PATCH v2 19/19] docs: sched-bwc.rst: fix a typo on a doc name 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=20210407113934.1a61ad9e@coco.lan \
--to=mchehab+huawei@kernel.org \
--cc=alexs@kernel.org \
--cc=bobwxc@email.cn \
--cc=corbet@lwn.net \
--cc=federico.vaga@vaga.pv.it \
--cc=grandmaster@al2klimov.de \
--cc=gregkh@linuxfoundation.org \
--cc=harryxiyou@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@leemhuis.info \
/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;
as well as URLs for NNTP newsgroup(s).