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

Re: What's cooking in git.git (Oct 2024, #08; Tue, 15)

From
Taylor Blau <me@ttaylorr.com>
Date
Oct 16, 2024, 21:10 UTC
Message-ID
<ZxArvQMURgclzEFt@nand.local>
In-Reply-To
<CAPSxiM_=9qjcrJRiwsSCOy-DvkmZH1ooNqLE-DGJJmtfYbVs9A@mail.gmail.com>
On Wed, Oct 16, 2024 at 01:36:49AM +0000, Usman Akinyemi wrote:
Show 8 quoted lines
> > * ua/t3404-cleanup (2024-10-14) 3 commits
> >  - parse: replace atoi() with strtoul_ui() and strtol_i()
> >  - t3404: replace test with test_line_count()
> >  - t3404: avoid losing exit status with focus on `git show` and `git cat-file`
>
> Hi Taylor, I sent a message regarding this.
> https://public-inbox.org/git/CAPSxiM-Cn8ZSC+LzRfeyY+Z_Vfj=DguweQ+ZjC4dau-Z64dnWg@mail.gmail.com/T/#t,
> kindly check. Thank you

Thanks, I had seen this message, but it is still not clear to me what the difference between these two are:

  https://public-inbox.org/git/pull.1805.v7.git.git.1728315124.gitgitgadget@gmail.com/#t
  https://public-inbox.org/git/pull.1810.git.git.1728774574.gitgitgadget@gmail.com/#t

Can you respond in either one of those threads which one I should keep? If the answer is "both", please let me know here.

In the future, please trim your email before responding When responding to a "What's cooking" message, it's common to quote only the topic(s) that you are responding to.

Thanks, Taylor

Previous: Usman AkinyemiNext: Usman Akinyemi
Message 4 of 5 in “What's cooking in git.git (Oct 2024, #08; Tue, 15)”
  1. Taylor BlauOct 16, 2024
  2. Taylor BlauOct 16, 2024
  3. Usman AkinyemiOct 16, 2024
  4. Taylor BlauOct 16, 2024
  5. Usman AkinyemiOct 17, 2024

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.