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

Re: [PATCH] doc: fix typos via codespell

From
Junio C Hamano <gitster@pobox.com>
Date
May 28, 2026, 20:37 UTC
Message-ID
<xmqq1pevjmoj.fsf@gitster.g>
In-Reply-To
<a48b62b8-2fc3-43be-a5e3-22189efef0ef@app.fastmail.com>
"Kristoffer Haugsbakk" <kristofferhaugsbakk@fastmail.com> writes:
Show 17 quoted lines
> On Sun, May 10, 2026, at 00:14, Kristoffer Haugsbakk wrote:
>> On Wed, May 6, 2026, at 12:15, Andrew Kreimer wrote:
>>> There are some typos in the documentation, comments, etc.
>>> Fix them via codespell.
>>>
>>> Signed-off-by: Andrew Kreimer <algonell@gmail.com>
>>> ---
>>>[snip]
>
> I went through the typos in my previous message and with the exception
> of `po/` they all look good. They are all either documentation typos
> or typos in code comments. And they are all legitimate, in other words
> not false positives.
>
> With Junio’s email in mind, I think a second version which just drops
> the `po/` and git-gui typo fixes would be good. Since they are different
> projects.
Thanks!.
Previous: Kristoffer HaugsbakkNext: Junio C Hamano
Message 4 of 17 in “doc: fix typos via codespell”
  1. doc: fix typos via codespellAndrew Kreimer, May 6, 2026
  2. Kristoffer HaugsbakkMay 9, 2026
  3. Kristoffer HaugsbakkMay 28, 2026
  4. Junio C HamanoMay 28, 2026
  5. Junio C HamanoMay 10, 2026
  6. Weijie YuanMay 23, 2026
  7. docs: fix typos and grammarWeijie Yuan, May 29, 2026
  8. Junio C HamanoJun 1, 2026
  9. Weijie YuanJun 2, 2026
  10. Weijie YuanJun 2, 2026
  11. doc: fix typos via codespellAndrew Kreimer, May 31, 2026
  12. Junio C HamanoJun 1, 2026
  13. Kristoffer HaugsbakkJun 1, 2026
  14. doc: fix typos via codespellAndrew Kreimer, Jun 2, 2026
  15. Junio C HamanoJun 2, 2026
  16. Johannes SchindelinJun 6, 2026
  17. Junio C HamanoJun 8, 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.