From: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
To: Linux Doc Mailing List <linux-doc@vger.kernel.org>
Cc: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>,
Mauro Carvalho Chehab <mchehab@infradead.org>,
linux-kernel@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>,
Harry Wei <harryxiyou@gmail.com>,
linux-kernel@zh-kernel.org
Subject: [PATCH 3/9] docs: zh_CN: fix location of oops-tracing.txt
Date: Tue, 26 Jun 2018 06:49:05 -0300 [thread overview]
Message-ID: <46a7c7ebc4b1d64f2d73fa3e9d47c0eb40685486.1530005114.git.mchehab+samsung@kernel.org> (raw)
In-Reply-To: <cover.1530005114.git.mchehab+samsung@kernel.org>
In-Reply-To: <cover.1530005114.git.mchehab+samsung@kernel.org>
This file was merged with bug-hunting. Make the translation
to point for its new location.
Fixes: f226e460875d ("admin-guide: merge oops-tracing with bug-hunting")
Signed-off-by: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
---
Documentation/translations/zh_CN/oops-tracing.txt | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/Documentation/translations/zh_CN/oops-tracing.txt b/Documentation/translations/zh_CN/oops-tracing.txt
index 41ab53cc0e83..a893f04dfd5d 100644
--- a/Documentation/translations/zh_CN/oops-tracing.txt
+++ b/Documentation/translations/zh_CN/oops-tracing.txt
@@ -1,4 +1,4 @@
-Chinese translated version of Documentation/admin-guide/oops-tracing.rst
+Chinese translated version of Documentation/admin-guide/bug-hunting.rst
If you have any comment or update to the content, please contact the
original document maintainer directly. However, if you have a problem
@@ -8,7 +8,7 @@ or if there is a problem with the translation.
Chinese maintainer: Dave Young <hidave.darkstar@gmail.com>
---------------------------------------------------------------------
-Documentation/admin-guide/oops-tracing.rst 的中文翻译
+Documentation/admin-guide/bug-hunting.rst 的中文翻译
如果想评论或更新本文的内容，请直接联系原文档的维护者。如果你使用英文
交流有困难的话，也可以向中文版维护者求助。如果本翻译更新不及时或者翻
--
2.17.1
next prev parent reply other threads:[~2018-06-26 9:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-26 9:49 [PATCH 0/9] Fix references for some missing documentation files Mauro Carvalho Chehab
2018-06-26 9:49 ` [PATCH 1/9] scripts/documentation-file-ref-check: remove some false positives Mauro Carvalho Chehab
2018-06-26 9:49 ` [PATCH 2/9] scripts/documentation-file-ref-check: ignore sched-pelt false positive Mauro Carvalho Chehab
2018-06-26 9:49 ` Mauro Carvalho Chehab [this message]
2018-06-26 9:49 ` [PATCH 4/9] devicectree: bindings: fix location of leds common file Mauro Carvalho Chehab
2018-06-26 14:38 ` Pavel Machek
2018-06-26 19:41 ` Jacek Anaszewski
2018-06-26 9:49 ` [PATCH 5/9] MAINTAINERS: fix location of ina2xx.txt device tree file Mauro Carvalho Chehab
2018-06-26 9:49 ` [PATCH 6/9] gpio.h: fix location of gpio legacy documentation Mauro Carvalho Chehab
2018-06-29 12:36 ` Linus Walleij
2018-06-26 9:49 ` [PATCH 7/9] networking: e100.rst: Get rid of Sphinx warnings Mauro Carvalho Chehab
2018-06-26 9:49 ` [PATCH 8/9] networking: e1000.rst: " Mauro Carvalho Chehab
2018-06-26 9:49 ` [PATCH 9/9] docs: histogram.txt: convert it to ReST file format Mauro Carvalho Chehab
2018-06-26 14:20 ` Steven Rostedt
2018-07-02 17:27 ` [PATCH 0/9] Fix references for some missing documentation files Jonathan Corbet
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=46a7c7ebc4b1d64f2d73fa3e9d47c0eb40685486.1530005114.git.mchehab+samsung@kernel.org \
--to=mchehab+samsung@kernel.org \
--cc=corbet@lwn.net \
--cc=harryxiyou@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kernel@zh-kernel.org \
--cc=mchehab@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
all inboxes | Powered by JetHome®