linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Chucheng Luo <luochucheng@vivo.com>
Cc: alex.shi@linux.alibaba.com, Harry Wei <harryxiyou@gmail.com>,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	opensource.kernel@vivo.com
Subject: Re: [PATCH v6,RESEND] Translate debugfs.txt into Chinese and link it to the index.
Date: Mon, 20 Apr 2020 17:10:42 -0600	[thread overview]
Message-ID: <20200420171042.66462fe0@lwn.net> (raw)
In-Reply-To: <20200408021528.14062-1-luochucheng@vivo.com>

On Wed,  8 Apr 2020 10:15:18 +0800
Chucheng Luo <luochucheng@vivo.com> wrote:

> Translate Documentation/filesystems/debugfs.txt into Chinese.
> 
> Signed-off-by: Chucheng Luo <luochucheng@vivo.com>
> ---
> Changelog:
> v6:
>  - keep each line less than 80 chars, but also keep each line full
>  - remove redundant '=' in caption and all other subheadings
>  - send the patch with 'charset=UTF-8'

I went to apply this just now, but no such luck; this patch tries to
create an index.rst file, but it's already there due to another patch that
went in just over a month ago.  I really don't want to try to resolve a
merge conflict in a file I can't read...could I ask you, please, to rebase
this patch on top of current docs-next, then submit one more time?

Thanks,

jon

  parent reply	other threads:[~2020-04-20 23:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-08  2:15 [PATCH v6,RESEND] Translate debugfs.txt into Chinese and link it to the index Chucheng Luo
2020-04-08 10:56 ` Alex Shi
2020-04-20 23:10 ` Jonathan Corbet [this message]
2020-04-21  1:46   ` 罗楚成
2020-05-09  8:05 ` [PATCH] doc: zh_CN: add translatation for debugfs.txt Wang Wenhu
2020-05-15 17:30   ` 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=20200420171042.66462fe0@lwn.net \
    --to=corbet@lwn.net \
    --cc=alex.shi@linux.alibaba.com \
    --cc=harryxiyou@gmail.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luochucheng@vivo.com \
    --cc=opensource.kernel@vivo.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).