From: ally heev <allyheev@gmail.com>
To: Jonathan Corbet <corbet@lwn.net>, Alex Shi <alexs@kernel.org>,
Yanteng Si <si.yanteng@linux.dev>,
Dongliang Mu <dzm91@hust.edu.cn>,
Hu Haowen <2023002089@link.tyut.edu.cn>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
skhan@linuxfoundation.org, david.hunter.linux@gmail.com
Subject: Re: [PATCH v2] Documentation: fix dev-tools broken links in translations
Date: Wed, 22 Oct 2025 12:22:23 +0530 [thread overview]
Message-ID: <9e80ec7909b40e662ea719d97151b9e6dbf8faab.camel@gmail.com> (raw)
In-Reply-To: <87qzuwt3hk.fsf@trenco.lwn.net>
On Tue, 2025-10-21 at 14:16 -0600, Jonathan Corbet wrote:
> Ally Heev <allyheev@gmail.com> writes:
>
> > gdb and kgdb debugging documentation were moved to
> > Documentation/process/debugging/ as a part of
> > Commit d5af79c05e9382d38b8546dc5362381ce07ba3d1 ("Documentation: move
> > dev-tools debugging files to process/debugging/"), but translations/
> > were not updated. Fix them
> >
> > ---
> > Link: https://lore.kernel.org/all/20241210000041.305477-1-rdunlap@infradead.org/
> > Signed-off-by: Ally Heev <allyheev@gmail.com>
> > ---
> > Changes in v2:
> > - fix kgdb doc path in zh_TW/admin-guide/README.rst
> > - Please drop v1 of the patch. It is malformed. Link to v1: https://lore.kernel.org/r/20251020-aheev-fix-docs-dev-tools-broken-links-v1-1-5d127efec0b2@gmail.com
> Putting your signoff after the "---" line caused the tooling to not
> include it in the resulting commit. I've fixed that up this time, and
> added a Fixes: tag as well.
> Applied, thanks,
>
> jon
Sorry for that. b4 messed up the formatting
Regards,
Ally
prev parent reply other threads:[~2025-10-22 6:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-20 10:46 [PATCH v2] Documentation: fix dev-tools broken links in translations Ally Heev
2025-10-21 20:16 ` Jonathan Corbet
2025-10-22 6:52 ` ally heev [this message]
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=9e80ec7909b40e662ea719d97151b9e6dbf8faab.camel@gmail.com \
--to=allyheev@gmail.com \
--cc=2023002089@link.tyut.edu.cn \
--cc=alexs@kernel.org \
--cc=corbet@lwn.net \
--cc=david.hunter.linux@gmail.com \
--cc=dzm91@hust.edu.cn \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=si.yanteng@linux.dev \
--cc=skhan@linuxfoundation.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