git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] docs: fix typos

From
KHKristoffer Haugsbakk <kristofferhaugsbakk@fastmail.com>
Date
Jun 9, 2026, 06:34 UTC
Message-ID
<ef91b8fe-c794-4230-a298-43cebbf85e18@app.fastmail.com>
In-Reply-To
<20260604131457.19215-1-taahol@utu.fi>
On Thu, Jun 4, 2026, at 15:14, Tuomas Ahola wrote:
Show 8 quoted lines
> 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.
Show 8 quoted lines
>     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]
Previous: Junio C Hamano
Message 6 of 6 in “docs: fix typos”
  1. docs: fix typosTuomas Ahola, Jun 4, 2026
  2. Kristoffer HaugsbakkJun 4, 2026
  3. Tuomas AholaJun 4, 2026
  4. Weijie YuanJun 5, 2026
  5. Junio C HamanoJun 8, 2026
  6. Kristoffer HaugsbakkJun 9, 2026

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.