From: Jonathan Corbet <corbet@lwn.net>
To: Randy Dunlap <rdunlap@infradead.org>, linux-doc@vger.kernel.org
Cc: Randy Dunlap <rdunlap@infradead.org>,
Sebastian Fricke <sebastian.fricke@collabora.com>,
workflows@vger.kernel.org,
Jason Wessel <jason.wessel@windriver.com>,
Daniel Thompson <danielt@kernel.org>,
Douglas Anderson <dianders@chromium.org>,
linux-debuggers@vger.kernel.org,
kgdb-bugreport@lists.sourceforge.net
Subject: Re: [PATCH] Documentation: move dev-tools debugging files to process/debugging/
Date: Fri, 06 Dec 2024 09:38:30 -0700 [thread overview]
Message-ID: <87h67gu5q1.fsf@trenco.lwn.net> (raw)
In-Reply-To: <20241204221720.66146-1-rdunlap@infradead.org>
Randy Dunlap <rdunlap@infradead.org> writes:
> Move gdb and kgdb debugging documentation to the dedicated
> debugging directory (Documentation/process/debugging/).
> Adjust the index.rst files to follow the file movement.
> Update location of kgdb.rst in MAINTAINERS file.
>
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
So ... since these are indeed development tools, I wonder if we should
leave a reference behind in case people are looking for them there?
jon
next prev parent reply other threads:[~2024-12-06 16:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-04 22:17 Randy Dunlap
2024-12-04 23:07 ` Doug Anderson
2024-12-04 23:09 ` Randy Dunlap
2024-12-05 9:09 ` Sebastian Fricke
2024-12-05 17:08 ` Randy Dunlap
2024-12-06 16:38 ` Jonathan Corbet [this message]
2024-12-06 23:57 ` Randy Dunlap
2024-12-07 8:50 ` Sebastian Fricke
2024-12-07 23:11 ` Randy Dunlap
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=87h67gu5q1.fsf@trenco.lwn.net \
--to=corbet@lwn.net \
--cc=danielt@kernel.org \
--cc=dianders@chromium.org \
--cc=jason.wessel@windriver.com \
--cc=kgdb-bugreport@lists.sourceforge.net \
--cc=linux-debuggers@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=sebastian.fricke@collabora.com \
--cc=workflows@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