linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Hu Haowen <src.res.211@gmail.com>
Cc: Hu Haowen <src.res.211@gmail.com>,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Subject: Re: [PATCH v3] docs/zh_TW: update contents for zh_TW
Date: Tue, 10 Oct 2023 13:07:17 -0600	[thread overview]
Message-ID: <87a5sq70uy.fsf@meer.lwn.net> (raw)
In-Reply-To: <20231010050727.49212-1-src.res.211@gmail.com>

[adding Konstantin]

Hu Haowen <src.res.211@gmail.com> writes:

> The content of zh_TW was too outdated comparing to the original files.
> Consequently carry out improvements in order to both keep track of sources
> and fix several grammatical mistakes in traditional Chinese.
>
> This is a thorough rewrite of the previous patch:
>     https://lore.kernel.org/linux-doc/20230807120006.6361-1-src.res.211@gmail.com/
> in order to get rid of text damage and merging errors, created based on
> linux-next (date: Oct. 9, 2023).
>
> Signed-off-by: Hu Haowen <src.res.211@gmail.com>

So this patch still isn't showing up in lore, with the result that b4
will not work with it.  The thing is, it *does* make it through vger,
and has landed in the LWN archive:

  https://lwn.net/ml/linux-kernel/20231010050727.49212-1-src.res.211%40gmail.com/

Might lore be dropping it because it consists of one big attachment?
Putting your patches inline would be the right thing to do in any case.

Rather than force another round, I've tried to the patch directly (but
see below), but it would be good to figure out why lore doesn't like it.
Konstantin, any ideas?

[Hmm...even weirder...v2, sent on Sep 25, wasn't in lore when I looked
on October 3 - but it *is* there now:

  https://lore.kernel.org/lkml/20230925052311.20992-1-src.res.211@gmail.com/

I'll admit to being entirely confused.]

The patch itself adds a whole bunch of new warnings, appended below, so
I've unapplied it again.  We have been through a few too many rounds on
this, please do not resend until you have verified that it applies and
builds correctly.

Thanks,

jon

New warnings:

Documentation/translations/zh_TW/arch/index.rst:8: WARNING: toctree contains reference to nonexisting document 'translations/zh_TW/riscv/index'
Documentation/translations/zh_TW/arch/loongarch/introduction.rst:325: WARNING: duplicate label loongarch-references-zh_cn, other instance in Documentation/translations/zh_CN/arch/loongarch/introduction.rst
Documentation/translations/zh_TW/process/embargoed-hardware-issues.rst:25: WARNING: duplicate label zh_contact, other instance in Documentation/translations/zh_CN/process/embargoed-hardware-issues.rst
Documentation/translations/zh_TW/process/submitting-patches.rst:54: WARNING: duplicate label zh_describe_changes, other instance in Documentation/translations/zh_CN/process/submitting-patches.rst
Documentation/translations/zh_TW/process/submitting-patches.rst:137: WARNING: duplicate label zh_split_changes, other instance in Documentation/translations/zh_CN/process/submitting-patches.rst
Documentation/translations/zh_TW/process/submitting-patches.rst:270: WARNING: duplicate label zh_resend_reminders, other instance in Documentation/translations/zh_CN/process/submitting-patches.rst
Documentation/translations/zh_TW/process/submitting-patches.rst:451: WARNING: duplicate label zh_the_canonical_patch_format, other instance in Documentation/translations/zh_CN/process/submitting-patches.rst
Documentation/translations/zh_TW/process/submitting-patches.rst:556: WARNING: duplicate label zh_backtraces, other instance in Documentation/translations/zh_CN/process/submitting-patches.rst
Documentation/translations/zh_TW/process/submitting-patches.rst:575: WARNING: duplicate label zh_explicit_in_reply_to, other instance in Documentation/translations/zh_CN/process/submitting-patches.rst

       reply	other threads:[~2023-10-10 19:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20231010050727.49212-1-src.res.211@gmail.com>
2023-10-10 19:07 ` Jonathan Corbet [this message]
2023-10-10 19:35   ` [PATCH v3] docs/zh_TW: update contents for zh_TW Konstantin Ryabitsev
2023-10-10 19:52     ` 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=87a5sq70uy.fsf@meer.lwn.net \
    --to=corbet@lwn.net \
    --cc=konstantin@linuxfoundation.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=src.res.211@gmail.com \
    /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).