All of lore.kernel.org
 help / color / mirror / Atom feed
From: Federico Vaga <federico.vaga@vaga.pv.it>
To: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
Cc: Linux Doc Mailing List <linux-doc@vger.kernel.org>,
	Jonathan Corbet <corbet@lwn.net>,
	"Alexander A. Klimov" <grandmaster@al2klimov.de>,
	Alex Shi <alexs@kernel.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Thorsten Leemhuis <linux@leemhuis.info>,
	Wu XiangCheng <bobwxc@email.cn>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 6/8] docs: replace transation references for reporting-bugs.rst
Date: Sat, 10 Apr 2021 00:04:03 +0200	[thread overview]
Message-ID: <028fa780f186689cddfba701b87c4c87@vaga.pv.it> (raw)
In-Reply-To: <3c7eb94992f7d85d75c8faf82c6a4690b2666951.1617972339.git.mchehab+huawei@kernel.org>

On 2021-04-09 14:47, 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")
> Acked-by: Wu XiangCheng <bobwxc@email.cn>
> Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
> ---
>  Documentation/translations/it_IT/process/howto.rst            | 2 +-

Acked-by: Federico Vaga <federico.vaga@vaga.pv.it>

>  Documentation/translations/ja_JP/howto.rst                    | 2 +-
>  Documentation/translations/zh_CN/SecurityBugs                 | 2 +-
>  .../translations/zh_CN/admin-guide/reporting-issues.rst       | 4 ++--
>  Documentation/translations/zh_CN/process/howto.rst            | 2 +-
>  5 files changed, 6 insertions(+), 6 deletions(-)

-- 
Federico Vaga

  reply	other threads:[~2021-04-09 22:04 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-09 12:47 [PATCH v3 0/8] Fix broken documentation file references Mauro Carvalho Chehab
2021-04-09 12:47 ` [PATCH v3 1/8] dt-bindings: don't use ../dir for doc references Mauro Carvalho Chehab
2021-04-09 16:30   ` Rob Herring
2021-04-09 19:18   ` Rob Herring
2021-04-09 12:47 ` [PATCH v3 2/8] dt-bindings: fix references for iio-bindings.txt Mauro Carvalho Chehab
2021-04-09 16:28   ` Rob Herring
2021-04-09 19:18   ` Rob Herring
2021-04-09 12:47 ` [PATCH v3 3/8] dt-bindings:iio:adc: update motorola,cpcap-adc.yaml reference Mauro Carvalho Chehab
2021-04-09 19:23   ` Rob Herring
2021-04-09 12:47 ` [PATCH v3 4/8] docs: update sysfs-platform_profile.rst reference Mauro Carvalho Chehab
2021-04-09 12:47 ` [PATCH v3 5/8] docs: vcpu-requests.rst: fix reference for atomic ops Mauro Carvalho Chehab
2021-04-15 16:08   ` Paolo Bonzini
2021-04-09 12:47 ` [PATCH v3 6/8] docs: replace transation references for reporting-bugs.rst Mauro Carvalho Chehab
2021-04-09 22:04   ` Federico Vaga [this message]
2021-04-09 12:47 ` [PATCH v3 7/8] docs: translations/zh_CN: fix a typo at 8.Conclusion.rst Mauro Carvalho Chehab
2021-04-09 12:47 ` [PATCH v3 8/8] 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=028fa780f186689cddfba701b87c4c87@vaga.pv.it \
    --to=federico.vaga@vaga.pv.it \
    --cc=alexs@kernel.org \
    --cc=bobwxc@email.cn \
    --cc=corbet@lwn.net \
    --cc=grandmaster@al2klimov.de \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@leemhuis.info \
    --cc=mchehab+huawei@kernel.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 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.