All of lore.kernel.org
 help / color / mirror / Atom feed
From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Pratyush Yadav <pratyush@kernel.org>,
	 Richard Weinberger <richard@nod.at>,
	 Tudor Ambarus <Tudor.Ambarus@linaro.org>,
	 Vignesh Raghavendra <vigneshr@ti.com>,
	 Frieder Schrempf <frieder.schrempf@kontron.de>,
	 Michael Walle <michael@walle.cc>,
	linux-mtd@lists.infradead.org
Subject: Re: [GIT PULL] mtd: Changes for 6.17
Date: Tue, 05 Aug 2025 09:47:21 +0200	[thread overview]
Message-ID: <87fre6i512.fsf@bootlin.com> (raw)
In-Reply-To: <CAHk-=wjxPV1NGZokCyg2su=y1nmJFXTb4asrosw_W+yyqNaq_w@mail.gmail.com> (Linus Torvalds's message of "Mon, 4 Aug 2025 08:53:14 -0700")

Hello,

On 04/08/2025 at 08:53:14 -07, Linus Torvalds <torvalds@linux-foundation.org> wrote:

> On Mon, 4 Aug 2025 at 07:40, Pratyush Yadav <pratyush@kernel.org> wrote:
>>
>> >
>> > I'm fine either ways, but I assumed until now that the preferred form
>> > was plain text descriptions.
>>
>> Okay, fair enough. I can do plain text next time around.
>
> I'm actually fine either way - what I care about is that it's a
> human-readable explanation of what is going on, and what I get when I
> pull.

[...]

> (And yes, I often find myself to be that person: I bisect some issue
> pretty much every single merge window, and while I usually have a good
> idea of what is going on, and just trust "git bisect" to do the right
> thing, I *do* end up looking back at merges to see where I am in the
> bisection process)

:)

> It can be bullet points when that makes sense, or it can be more of a
> plain text explanation of the background to a change.

Thanks Linus for the detailed answer.

Pratyush, I guess I'll switch back to bullet points to highlight what
are the important changes, so you can stick to what you were doing. If I
feel like plain text would be sometimes better I might mix both
occasionally.

Thanks,
Miquèl

______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/

      reply	other threads:[~2025-08-05  7:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-31 16:59 [GIT PULL] mtd: Changes for 6.17 Miquel Raynal
2025-07-31 20:51 ` pr-tracker-bot
2025-08-01 14:47 ` Pratyush Yadav
2025-08-01 15:01   ` Miquel Raynal
2025-08-04 14:40     ` Pratyush Yadav
2025-08-04 15:53       ` Linus Torvalds
2025-08-05  7:47         ` Miquel Raynal [this message]

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=87fre6i512.fsf@bootlin.com \
    --to=miquel.raynal@bootlin.com \
    --cc=Tudor.Ambarus@linaro.org \
    --cc=frieder.schrempf@kontron.de \
    --cc=linux-mtd@lists.infradead.org \
    --cc=michael@walle.cc \
    --cc=pratyush@kernel.org \
    --cc=richard@nod.at \
    --cc=torvalds@linux-foundation.org \
    --cc=vigneshr@ti.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.