From: Greg KH <gregkh@linuxfoundation.org>
To: Thorsten Leemhuis <linux@leemhuis.info>
Cc: Jonathan Corbet <corbet@lwn.net>,
Randy Dunlap <rdunlap@infradead.org>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
Harry Wei <harryxiyou@gmail.com>,
Alex Shi <alex.shi@linux.alibaba.com>,
Federico Vaga <federico.vaga@vaga.pv.it>
Subject: Re: [PATCH v1 1/4] docs: make reporting-issues.rst official and delete reporting-bugs.rst
Date: Tue, 30 Mar 2021 16:51:29 +0200 [thread overview]
Message-ID: <YGM68Q0+aeNgjsdy@kroah.com> (raw)
In-Reply-To: <49c674c2d304d87e6259063580fda05267e8c348.1617113469.git.linux@leemhuis.info>
On Tue, Mar 30, 2021 at 04:13:04PM +0200, Thorsten Leemhuis wrote:
> Removing Documentation/admin-guide/reporting-bugs.rst will break links
> in some of the translations. I was unsure if simply changing them to
> Documentation/admin-guide/reporting-issue.rst was wise, so I didn't
> touch anything for now and CCed the maintainers for the Chinese and
> Italian translation. I couldn't find one for the Japanse translation.
>
> Please advice. For completeness, this are the places where things will
> break afaics:
>
> $ grep -ri 'reporting-bugs.rst' Documentation/
> Documentation/translations/zh_CN/SecurityBugs:是有帮助的信息，那就请重温一下admin-guide/reporting-bugs.rst文件中的概述过程。任
> Documentation/translations/zh_CN/process/howto.rst:内核源码主目录中的:ref:`admin-guide/reporting-bugs.rst <reportingbugs>`
> 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”中的旧文字非常相似。它和它
> Documentation/translations/it_IT/process/howto.rst:Il file admin-guide/reporting-bugs.rst nella cartella principale del kernel
> Documentation/translations/ja_JP/howto.rst:admin-guide/reporting-bugs.rstはカーネルバグらしいものについてどうレポー
Traditionally translations catch up much later on, you shouldn't have to
worry about them the authors will clean them up and submit patches for
them when they get the chance.
thanks,
greg k-h
next prev parent reply other threads:[~2021-03-30 14:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-30 14:13 [PATCH v1 0/4] Improve reporting-issues.rst and make it official Thorsten Leemhuis
2021-03-30 14:13 ` [PATCH v1 1/4] docs: make reporting-issues.rst official and delete reporting-bugs.rst Thorsten Leemhuis
2021-03-30 14:51 ` Greg KH [this message]
2021-03-31 19:47 ` Jonathan Corbet
2021-04-05 7:43 ` Thorsten Leemhuis
2021-03-30 14:51 ` Greg KH
2021-03-31 8:33 ` Wu X.C.
2021-04-01 4:59 ` Alex Shi
2021-03-30 14:13 ` [PATCH v1 2/4] MAINTAINERS: add entry for Documentation/admin-guide/reporting-issues.rst Thorsten Leemhuis
2021-03-30 14:13 ` [PATCH v1 3/4] docs: reporting-issues.rst: reshuffle and improve TLDR Thorsten Leemhuis
2021-03-30 15:17 ` Thorsten Leemhuis
2021-03-30 14:13 ` [PATCH v1 4/4] docs: reporting-issues: reduce quoting and assorted fixes Thorsten Leemhuis
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=YGM68Q0+aeNgjsdy@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=alex.shi@linux.alibaba.com \
--cc=corbet@lwn.net \
--cc=federico.vaga@vaga.pv.it \
--cc=harryxiyou@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@leemhuis.info \
--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