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

Re: What's cooking in git.git (Sep 2025, #06; Mon, 15)

From
Patrick Steinhardt <ps@pks.im>
Date
Sep 18, 2025, 05:52 UTC
Message-ID
<aMueCwl6hfZRJ_qN@pks.im>
In-Reply-To
<xmqqv7limi1b.fsf@gitster.g>
On Tue, Sep 16, 2025 at 10:19:44AM -0700, Junio C Hamano wrote:
Show 9 quoted lines
> Jeff King <peff@peff.net> writes:
> 
> > That said, it is not really that big an issue and I am fine with any
> > fix. If you want to document how the history unfolded, then I think an
> > evil merge shows that (neither topic had a problem on its own, but when
> > merged we needed to adjust the result). And it is probably the least
> > amount of work. ;)
> 
> That's also fine, too.  Let me try that ;-)

Yeah, an evil merge probably is the easiest way, and I see that's what you did in b501ac6a85 (Merge branch 'ps/odb-clean-stale-wrappers' into seen, 2025-09-17) now. Thanks!

Patrick
Previous: Junio C HamanoNext: Kristoffer Haugsbakk
Message 6 of 7 in “What's cooking in git.git (Sep 2025, #06; Mon, 15)”
  1. Junio C HamanoSep 15, 2025
  2. Patrick SteinhardtSep 16, 2025
  3. Junio C HamanoSep 16, 2025
  4. Jeff KingSep 16, 2025
  5. Junio C HamanoSep 16, 2025
  6. Patrick SteinhardtSep 18, 2025
  7. Kristoffer HaugsbakkSep 16, 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.