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

Re: What's cooking in git.git (Nov 2019, #02; Fri, 8)

From
Elijah Newren <newren@gmail.com>
Date
Nov 8, 2019, 16:44 UTC
Message-ID
<CABPp-BHLAdTDaooQu2YXGcTEtqQrOwZ7cuQNhNuFEnV-yA0FiA@mail.gmail.com>
In-Reply-To
<xmqqeeyin4kx.fsf@gitster-ct.c.googlers.com>
On Fri, Nov 8, 2019 at 12:43 AM Junio C Hamano <gitster@pobox.com> wrote:
Show 16 quoted lines
> * en/doc-typofix (2019-11-07) 11 commits
>  - Fix spelling errors in no-longer-updated-from-upstream modules
>  - multimail: fix a few simple spelling errors
>  - sha1dc: fix trivial comment spelling error
>  - Fix spelling errors in test commands
>  - Fix spelling errors in messages shown to users
>  - Fix spelling errors in names of tests
>  - Fix spelling errors in comments of testcases
>  - Fix spelling errors in code comments
>  - Prefer 'up-to-date' spelling
>  - Fix spelling errors in documentation outside of Documentation/
>  - Documentation: fix a bunch of typos, both old and new
>
>  Docfix.
>
>  Will merge to 'next'.

Wait! I thought we wanted to eject the uptodate vs. up-to-date patch. Do you want to do that, or do you want me to send a re-roll where the only change is removing that patch? (The other patches are fine to merge to next if you want.)

See https://public-inbox.org/git/CABPp-BECJezMeg1pZyQijkBDooA_834weeg_2hsZ1Vonm-tAEQ@mail.gmail.com/
Previous: Matheus Tavares BernardinoNext: Junio C Hamano
Message 4 of 5 in “What's cooking in git.git (Nov 2019, #02; Fri, 8)”
  1. Junio C HamanoNov 8, 2019
  2. Matheus Tavares BernardinoNov 8, 2019
  3. Matheus Tavares BernardinoNov 14, 2019
  4. Elijah NewrenNov 8, 2019
  5. Junio C HamanoNov 10, 2019

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.