Re: [PATCH] docs: fix typos

["Kristoffer Haugsbakk" <kristofferhaugsbakk@fastmail.com>]

On Thu, Jun 4, 2026, at 15:14, Tuomas Ahola wrote:
> Fix some typos and grammar errors in comments and documentation files.
>
> Signed-off-by: Tuomas Ahola <taahol@utu.fi>
> ---
>
> Notes:
>     Written mostly as an exercise on how to submit patches that depend
>     on other topics.

I’ve been thinking of how to handle typos for a few days now. ;) The
following does not apply to this submission since the maintainer said
that he will apply it.

Anyway, it struck me that you might sometimes want to apply the typofix
on top of the original branch *if* the branch is scheduled to be merged
to more than just `master`.

So e.g. this does *not* apply to topic kh/name-rev-custom-format since
that topic is not scheduled for a maintenance branch (`maint`). But:

>
>     $ git log --oneline --first-parent v2.54.0..
>     d19e9182ab (HEAD -> ta/typofixes) docs: fix typos
>     5a7e9cc03d Merge branch 'ta/approxidate-noon-fix'

Your topic is. See `RelNotes`:

    (merge b809304101 ta/approxidate-noon-fix later to maint).

So it might make sense in such cases to post a patch to
be applied on top of the topic.

Just a thought for later.

>     f03649d802 Merge branch 'kh/name-rev-custom-format'
>     023a226b4b Merge branch 'jc/neuter-sideband-fixup'
>
>     As can be seen, these topics have already graduated to master:
>
>     $ git cherry master
>     + d19e9182ab097a722e32d459a9a58c8985831e3b
>[snip]