linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Alex Shi <alex.shi@linux.alibaba.com>
Cc: harryxiyou@gmail.com, leoyang.li@nxp.com, linux-doc@vger.kernel.org
Subject: Re: [PATCH v2 00/59] Chinese docs translationn series 2
Date: Tue, 2 Apr 2019 10:00:25 -0600	[thread overview]
Message-ID: <20190402100025.27097923@lwn.net> (raw)
In-Reply-To: <20190401144506.49718-1-alex.shi@linux.alibaba.com>

On Mon,  1 Apr 2019 22:44:07 +0800
Alex Shi <alex.shi@linux.alibaba.com> wrote:

> This patch series add a few new docs in Chinese, updated 
> submitting-patches and howto docs, All docs rebased on Jon's
> docs-next branch.
> 
>     make htmldocs result show at:
>     http://176.122.172.82/translations/zh_CN/index.html

OK, I have applied the set.  A couple of notes/requests:

 - This set introduced this build error:

	Documentation/translations/zh_CN/process/coding-style.rst:3:
	WARNING: undefined label: codingsytle (if the link has no caption
	the label must precede a section header)

   I added the patch below to fix that.  Please be sure to build the docs
   after a series like this to ensure that no new warnings have been added.

 - This is a *lot* of stuff.  In the future, keeping each series smaller
   would be appreciated.

Thanks,

jon

From 5e3ec254e086f348346df3f00a6d372defd10d4e Mon Sep 17 00:00:00 2001
From: Jonathan Corbet <corbet@lwn.net>
Date: Tue, 2 Apr 2019 09:58:08 -0600
Subject: [PATCH] docs: Fix a build error in coding-style.rst

A reference typo caused an unsightly build error; fix it.

Signed-off-by: Jonathan Corbet <corbet@lwn.net>
---
 Documentation/translations/zh_CN/process/coding-style.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Documentation/translations/zh_CN/process/coding-style.rst b/Documentation/translations/zh_CN/process/coding-style.rst
index cab9ceafa267..5479c591c2f7 100644
--- a/Documentation/translations/zh_CN/process/coding-style.rst
+++ b/Documentation/translations/zh_CN/process/coding-style.rst
@@ -1,6 +1,6 @@
 .. include:: ../disclaimer-zh_CN.rst
 
-:Original: :ref:`Documentation/process/coding-style.rst <codingsytle>`
+:Original: :ref:`Documentation/process/coding-style.rst <codingstyle>`
 
 .. _cn_codingstyle:
 
-- 
2.20.1



           reply	other threads:[~2019-04-02 16:00 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20190401144506.49718-1-alex.shi@linux.alibaba.com>]

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=20190402100025.27097923@lwn.net \
    --to=corbet@lwn.net \
    --cc=alex.shi@linux.alibaba.com \
    --cc=harryxiyou@gmail.com \
    --cc=leoyang.li@nxp.com \
    --cc=linux-doc@vger.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 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).