Linux Documentation
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Purva Yeshi <purvayeshi550@gmail.com>
Cc: Bagas Sanjaya <bagasdotme@gmail.com>,
	Masami Hiramatsu <mhiramat@kernel.org>,
	Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
	Jonathan Corbet <corbet@lwn.net>,
	linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
	linux-doc@vger.kernel.org
Subject: Re: [PATCH v3 2/2] docs: tracing: Reduce maxdepth in index documentation
Date: Fri, 14 Mar 2025 08:41:55 -0400	[thread overview]
Message-ID: <20250314084155.20c3e662@batman.local.home> (raw)
In-Reply-To: <b1882a1f-3ed0-4307-8a34-3236bdfb79a6@gmail.com>

On Fri, 14 Mar 2025 14:26:37 +0530
Purva Yeshi <purvayeshi550@gmail.com> wrote:

> Thanks for the reference. I will keep this in mind for future patch 
> series and include a cover letter.

Note, a cover letter isn't really necessary here. Why? because these
are pretty much two agnostic patches. One fixes the maxdepth, the other
is changing the layout for readability.

Cover letters are best when there's a bigger picture being had. That
is, the patch series is set out to accomplish a single goal that is
broken up into little steps. A cover letter explains what the goal is
and why and how. Each patch after that explains what that patch is
doing (why and how), but from the focus of that particular change.

As these patches could theoretically be sent as two separate patches
and not as a series as they don't really share the same goal, a cover
letter's only purpose here would be to make the email thread look a
little nicer ;-)  But that's about it.

-- Steve

  reply	other threads:[~2025-03-14 12:42 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-12 12:47 [PATCH v3 2/2] docs: tracing: Reduce maxdepth in index documentation Purva Yeshi
2025-03-12 17:49 ` Steven Rostedt
2025-03-13  3:02   ` Bagas Sanjaya
2025-03-13 11:04     ` Steven Rostedt
2025-03-13 12:16       ` Bagas Sanjaya
2025-03-14  8:56         ` Purva Yeshi
2025-03-14 12:41           ` Steven Rostedt [this message]
2025-03-18 11:35             ` Purva Yeshi
2025-03-14  8:55   ` Purva Yeshi
2025-03-14 12:35     ` Steven Rostedt

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=20250314084155.20c3e662@batman.local.home \
    --to=rostedt@goodmis.org \
    --cc=bagasdotme@gmail.com \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=mhiramat@kernel.org \
    --cc=purvayeshi550@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox