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

Re: Can git change?

From
Junio C Hamano <gitster@pobox.com>
Date
Jan 23, 2021, 02:27 UTC
Message-ID
<xmqqh7n85qwd.fsf@gitster.c.googlers.com>
In-Reply-To
<CANiSa6gEJ8ezVLhHf+TkGpqvEwvb8HhqtU3ETKiopjLQj6E_QQ@mail.gmail.com>
Martin von Zweigbergk <martinvonz@gmail.com> writes:
> This is probably quite off topic for the thread, but I'm curious why
> you think it was a bad idea to have octopus merges in git.git's
> history (there seem to be 37 of them).

Octoupi in our history, at least the older ones, solve no real life problem; it only gives us "now we have something cool-looking that other people's version control systems never had", which is of dubious value.

And their presense makes bisection less efficient than it could be around them, which is a real downside.

Previous: Martin von ZweigbergkNext: Patricia B. C.
Message 5 of 12 in “Can git change?”
  1. Patricia B. C.Jan 22, 2021
  2. Christian CouderJan 22, 2021
  3. Junio C HamanoJan 22, 2021
  4. Martin von ZweigbergkJan 22, 2021
  5. Junio C HamanoJan 23, 2021
  6. RES: Can git change?Patricia B. C., Jan 23, 2021
  7. Johannes SchindelinJan 25, 2021
  8. Junio C HamanoJan 26, 2021
  9. Patricia B. C.Jan 26, 2021
  10. Daniel GruessoMar 9, 2021
  11. Johannes SchindelinMar 10, 2021
  12. Junio C HamanoMar 10, 2021

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.