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

Re: [PATCH 1/3] t6429: update comment to mention correct tool

From
Elijah Newren <newren@gmail.com>
Date
Nov 7, 2025, 22:40 UTC
Message-ID
<CABPp-BGchyC6BB2p7p-6qHvwcu5AV+VCAdTeR247F0VamsJkbQ@mail.gmail.com>
In-Reply-To
<2983385e-daeb-40c0-a8bc-fb8bd3b744a6@app.fastmail.com>

On Fri, Nov 7, 2025 at 6:36 AM Kristoffer Haugsbakk <kristofferhaugsbakk@fastmail.com> wrote:

Show 14 quoted lines
>
> On Mon, Nov 3, 2025, at 19:01, Elijah Newren via GitGitGadget wrote:
> > From: Elijah Newren <newren@gmail.com>
> >
> > A comment at the top of t6429 mentions why the test doesn't exercise git
> > rebase or git cherry-pick.  However, it claims that it uses `test-tool
> > fast-rebase`.  That was true when the comment was written, but commit
> > f920b0289ba3 (replay: introduce new builtin, 2023-11-24) changed it to
> > use git replay without updating this comment.
> >
> > We could potentially just strike this second comment, since git replay
> > is a bonified built-in, but perhaps the explanation about why it focuses
>
> s/bonified/bona fide/ ?

Yep, good catch. Got it fixed locally; will wait to see if any other feedback comes in.

Previous: Kristoffer HaugsbakkNext: Junio C Hamano
Message 6 of 9 in “Fix another crazy rename assertion”
  1. 0/3 Fix another crazy rename assertionElijah Newren via GitGitGadget, Nov 3, 2025
  2. 2/3 merge-ort: remove debugging crudElijah Newren via GitGitGadget, Nov 3, 2025
  3. 3/3 merge-ort: fix failing merges in special corner caseElijah Newren via GitGitGadget, Nov 3, 2025
  4. 1/3 t6429: update comment to mention correct toolElijah Newren via GitGitGadget, Nov 3, 2025
  5. Kristoffer HaugsbakkNov 7, 2025
  6. Elijah NewrenNov 7, 2025
  7. Junio C HamanoNov 17, 2025
  8. Elijah NewrenNov 17, 2025
  9. Junio C HamanoNov 17, 2025

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.