From: Tuomas Ahola <taahol@utu•fi>
To: Kristoffer Haugsbakk <kristofferhaugsbakk@fastmail•com>
Cc: <git@vger•kernel.org>
Subject: Re: [PATCH] docs: fix typos
Date: Thu, 4 Jun 2026 19:55:57 +0300 [thread overview]
Message-ID: <20260604165557.MWQuu%taahol@utu.fi> (raw)
In-Reply-To: <92fe3db2-83bd-4aa9-a1f4-bec01dfaf8ca@app.fastmail.com>
"Kristoffer Haugsbakk" <kristofferhaugsbakk@fastmail•com> wrote:
> On Thu, Jun 4, 2026, at 15:14, Tuomas Ahola wrote:
> > [PATCH] docs: fix typos
>
> The area `docs` isn’t correct since you are also changing comments in
> source files.
>
> `*` could be used (as in a wildcard). Other people have used other
> things for “treewide” changes.
>
Hmm, I took that from the other typofix patches we have currently in `seen`.
> > * The tm->tm_mday field has an additional logic of using negative values
> > * for date adjustments: -2 means yesterday and -3 the day before that,
> > - * and so on. The idea is to deref such adjustments until we are sure
> > + * and so on. The idea is to defer such adjustments until we are sure
>
> “deref” could have been “dereference” but this must indeed mean
> “defer”. We are putting off a decision until later.
>
Yes, that was my own typo. I always meant "defer".
> >
> > base-commit: 94f057755b7941b321fd11fec1b2e3ca5313a4e0
> > prerequisite-patch-id: f827362e061e199150f149dd36c67664c77406bc
> > prerequisite-patch-id: e5b32f0b916ec86eab6631b9bd9bafd639191765
> > [...]
> > prerequisite-patch-id: 083f554bc5e09ae54c6b545628196e11a9e90cea
>
> Okay, these must be all the non-merge commits from the topics you
> merged in.
>
That's true. Quite a list though.
Thanks for review!
prev parent reply other threads:[~2026-06-04 16:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-04 13:14 [PATCH] docs: fix typos Tuomas Ahola
2026-06-04 14:45 ` Kristoffer Haugsbakk
2026-06-04 16:55 ` Tuomas Ahola [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=20260604165557.MWQuu%taahol@utu.fi \
--to=taahol@utu$(echo .)fi \
--cc=git@vger$(echo .)kernel.org \
--cc=kristofferhaugsbakk@fastmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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