From: Jonathan Corbet <corbet@lwn.net>
To: Shuah Khan <skhan@linuxfoundation.org>,
Thorsten Leemhuis <linux@leemhuis.info>
Cc: sshefali021@gmail.com, kstewart@linuxfoundation.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH v2] docs: add workload-tracing document to admin-guide
Date: Mon, 30 Jan 2023 16:52:30 -0700 [thread overview]
Message-ID: <87o7qf4m2p.fsf@meer.lwn.net> (raw)
In-Reply-To: <021776e6-b37f-0a2e-41e0-5c09f9582c57@linuxfoundation.org>
Shuah Khan <skhan@linuxfoundation.org> writes:
> On 1/28/23 01:35, Thorsten Leemhuis wrote:
>> Adding another section that doesn't seem to a be a good fit feels a bit
>> like "making things worse than better". So wouldn't this maybe be a
>> good opportunity to create a totally new top-level section for
>> application developers and system integrators, even if it's tiny for
>> now? The audience is likely big enough to justify that -- and the topics
>> are likely different enough, too (of course sometimes there will be
>> overlap, as always). Any maybe it will help to bring other stuff over
>> from admin guide that is more targeted for application developers and
>> system integrators, which will help to get more structure into the
>> admin-guide.
>>
>
> I like the idea of creating a new top-level section for application developers
> and system integrators. I foresee this section growing and also we can look
> at other documents that are a good fit under this category and move them over.
>
> Jon, Thoughts on this.
The fit with the admin guide caught my attention as well, but I didn't
immediately have a better place to suggest. I am somewhat resistant to
creating another top-level directory; I really want to have *fewer* of
them. I certainly don't want to create one for a single document. My
inclination would be to leave it where it is for now; we can always
revisit this if it turns out we have a lot of material that justifies a
new book.
Thanks,
jon
next prev parent reply other threads:[~2023-01-30 23:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-27 23:46 [PATCH v2] docs: add workload-tracing document to admin-guide Shuah Khan
2023-01-28 3:14 ` Bagas Sanjaya
2023-01-30 23:19 ` Shuah Khan
2023-01-28 5:40 ` Randy Dunlap
2023-01-30 23:20 ` Shuah Khan
2023-01-28 8:35 ` Thorsten Leemhuis
2023-01-30 23:30 ` Shuah Khan
2023-01-30 23:52 ` Jonathan Corbet [this message]
2023-01-31 19:20 ` Shuah Khan
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=87o7qf4m2p.fsf@meer.lwn.net \
--to=corbet@lwn.net \
--cc=kstewart@linuxfoundation.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@leemhuis.info \
--cc=skhan@linuxfoundation.org \
--cc=sshefali021@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.