mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Dhruva Gole <d-gole@ti.com>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	Dhruva Gole <d-gole@ti.com>
Subject: Re: [PATCH] Documentation: index: Minor re-arrangement and improvements
Date: Tue, 23 Jan 2024 14:51:27 -0700	[thread overview]
Message-ID: <87bk9bk9b4.fsf@meer.lwn.net> (raw)
In-Reply-To: <20240104073317.19709-1-d-gole@ti.com>

Dhruva Gole <d-gole@ti.com> writes:

> * It seems odd that a develper is forced to look at the licensing rules
>   even before they get to the doc or coding guide.
>   This belongs under the "Working with the development community" / "All
>   development docs" page where it does reside even today.
> * Rearrange the section for Internal API manuals to go lower because
>   generally one would want to look at the tools and processes and admin
>   guide pages first and then move onto something deeper like the API
>   manuals.
> * Reword the Dev tools section and title to something a bit more suitable.
>
> Signed-off-by: Dhruva Gole <d-gole@ti.com>

As a general rule, multiple items in the changelog like this suggest
that you need to break a patch up.

In this case, though, I guess I don't see the reason why we would want
to churn this page this way.  The ordering of the items on the front
page was thought through and discussed the last time we did this; why
should we revisit it now?

Thanks,

jon

  reply	other threads:[~2024-01-23 21:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-04  7:33 Dhruva Gole
2024-01-23 21:51 ` Jonathan Corbet [this message]
2024-01-24  6:21   ` Dhruva Gole

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=87bk9bk9b4.fsf@meer.lwn.net \
    --to=corbet@lwn.net \
    --cc=d-gole@ti.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®