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

wishlist: make it possible to amend commit messages after push to remote

From
JHJarkko Hietaniemi <jhi@iki.fi>
Date
Aug 7, 2015, 00:23 UTC
Message-ID
<55C3FA66.90805@iki.fi>

Not for the first time, and probably not for the last, I pushed a commit upstream without adding a link for the bug report as I was meaning to.

Or it could have been...
- Simple typos.
- Broken URLs.
- The impossibility of two consecutive commits referring to each other
because the older one cannot know what the newer one will be called.
- The following morning / 5 minutes / 5 second later thinking of
an additional factoid that would've been great to have in the
commit message.

In general, I find the fact that once a commit has left the building, it goes into your permanent record, and cannot be changed, ever, to be very, very annoying. I get the cryptographic "sealing" with all the preceding changes, but...

Not that I've thought this through... but couldn't there be a bunch of "aliases" (new SHAs) for a commit? The original one being the "master", but as/if the commit message is changed, it could get new SHAs. Sort of separating the real data of the commit, and the metadata?

Next: Kevin Daudt
Message 1 of 9 in “wishlist: make it possible to amend commit messages after push to remote”
  1. Jarkko HietaniemiAug 7, 2015
  2. Kevin DaudtAug 7, 2015
  3. Jarkko HietaniemiAug 7, 2015
  4. Philip OakleyAug 7, 2015
  5. Junio C HamanoAug 7, 2015
  6. Jarkko HietaniemiAug 7, 2015
  7. Johannes SchindelinAug 7, 2015
  8. Jarkko HietaniemiAug 7, 2015
  9. Jeff KingAug 8, 2015

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.