mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Min-Hua Chen <minhuadotchen@gmail.com>,
	Hu Haowen <src.res@email.cn>, Jonathan Corbet <corbet@lwn.net>
Cc: linux-doc-tw-discuss@lists.sourceforge.net,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] docs: sparse: fix invalid link addresses
Date: Fri, 4 Aug 2023 11:47:48 -0700	[thread overview]
Message-ID: <bfab7c5b-e4d3-d8d9-afab-f43c0cdf26cf@infradead.org> (raw)
In-Reply-To: <20230804112320.35592-1-minhuadotchen@gmail.com>



On 8/4/23 04:23, Min-Hua Chen wrote:
> The http and git links are invalid, replace them with valid links.
> 
> Signed-off-by: Min-Hua Chen <minhuadotchen@gmail.com>

Reviewed-by: Randy Dunlap <rdunlap@infradead.org>

It would be good if someone would update/modify this
sparse.txt file to be in Documentation/translation/zh_TW/dev-tools/
and convert it to sparse.rst (IMO).

Thanks.

> ---
>  Documentation/translations/zh_TW/sparse.txt | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/Documentation/translations/zh_TW/sparse.txt b/Documentation/translations/zh_TW/sparse.txt
> index c9acb2c926cb..6d2d088b1060 100644
> --- a/Documentation/translations/zh_TW/sparse.txt
> +++ b/Documentation/translations/zh_TW/sparse.txt
> @@ -66,11 +66,11 @@ __bitwise"類型。
>  
>  你可以從 Sparse 的主頁獲取最新的發布版本:
>  
> -	http://www.kernel.org/pub/linux/kernel/people/josh/sparse/
> +	https://www.kernel.org/pub/software/devel/sparse/dist/
>  
>  或者,你也可以使用 git 克隆最新的 sparse 開發版本:
>  
> -	git://git.kernel.org/pub/scm/linux/kernel/git/josh/sparse.git
> +        git://git.kernel.org/pub/scm/devel/sparse/sparse.git
>  
>  一旦你下載了源碼,只要以普通用戶身份運行:
>  

-- 
~Randy

  reply	other threads:[~2023-08-04 18:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-04 11:23 Min-Hua Chen
2023-08-04 18:47 ` Randy Dunlap [this message]
2023-08-04 23:43   ` Min-Hua Chen
2023-08-11 20:29 ` 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=bfab7c5b-e4d3-d8d9-afab-f43c0cdf26cf@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=corbet@lwn.net \
    --cc=linux-doc-tw-discuss@lists.sourceforge.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=minhuadotchen@gmail.com \
    --cc=src.res@email.cn \
    /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®