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

Feature request: Allow to update commit ID in messages when rebasing

From
Giuseppe Crinò <giuscri@gmail.com>
Date
Apr 17, 2019, 20:35 UTC
Message-ID
<CAGV3M54XhRMDXdhbfTon5nRV59VOjw8W4YrNP63TqPYm8pxd8Q@mail.gmail.com>

The feature I'm asking is to add an extra-step during rebasing, checking whether there's a reference to a commit that's not going to be included in history and asks the user whether the heuristics is correct and if she wants to update those references.

Scenario: it can happen for a commit message to contain the ID of an
ancestor commit. A typical example is a commit with the message
"revert 01a9fe8". If 01a9fe8 and the commit that reverts it are
involved in a rebase the message "revert 01a9fe8" is no longer valid
-- the old 01a9fe8 has now a different hash. This will most likely be
ignored by the person who's rebasing but will let the other people
reading history confused.
Giuseppe
Next: Ævar Arnfjörð Bjarmason
Message 1 of 7 in “Feature request: Allow to update commit ID in messages when rebasing”
  1. Giuseppe CrinòApr 17, 2019
  2. Ævar Arnfjörð BjarmasonApr 17, 2019
  3. Junio C HamanoApr 18, 2019
  4. Jakub NarebskiApr 18, 2019
  5. Phil HordApr 18, 2019
  6. Giuseppe CrinòApr 18, 2019
  7. Jakub NarebskiApr 19, 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.