From: Sebastian Fricke <sebastian.fricke@collabora.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org, 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: Sat, 7 Dec 2024 09:50:56 +0100 [thread overview]
Message-ID: <20241207085056.fcnoqov3kd5rjqft@basti-XPS-13-9310> (raw)
In-Reply-To: <0e5dbbbe-4cd8-49d2-a440-7e1acd7d40e9@infradead.org>
Hey Randy,
On 06.12.2024 15:57, Randy Dunlap wrote:
>
>
>On 12/6/24 8:38 AM, Jonathan Corbet wrote:
>> 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?
>
>As far as I'm concerned, all debug tools are development tools, so I'm back
>to all of /process/debugging/ should be somewhere else. ;)
I mean this is where things just simply overlap, because debugging is
part of the development process and all debugging tools are development
tools, so I think the question is not whether one of the two places is
the "correct" but instead the user should be able to find the necessary
information by navigating to any of the two places.
So I would say, lets add a reference in the index of the development
tools that highlights the documentation of the debugging tools which are
found in the development process documentation.
>
>cheers.
>--
>~Randy
Regards,
Sebastian Fricke
next prev parent reply other threads:[~2024-12-07 8:51 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
2024-12-06 23:57 ` Randy Dunlap
2024-12-07 8:50 ` Sebastian Fricke [this message]
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=20241207085056.fcnoqov3kd5rjqft@basti-XPS-13-9310 \
--to=sebastian.fricke@collabora.com \
--cc=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=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