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

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

From
JHJarkko Hietaniemi <jhi@iki.fi>
Date
Aug 7, 2015, 22:50 UTC
Message-ID
<55C5364C.6040904@iki.fi>
In-Reply-To
<a0b9f82a46f2887d3ff3fb392e2e4c2c@www.dscho.org>
On Friday-201508-07 15:38, Johannes Schindelin wrote:
> Speaking for myself, I actually like it that the entire metadata is part of the commit object, even the commit message. It makes the whole thing more reliable: one cannot claim that the commit does one thing on one day, and the next day all of a sudden claim that the commit does something completely different. Git's just really consistent the way it is.

Not that I expect anything to change.. but I'd like to point out again that I wasn't wishlisting "overwrite/replace/demolish the old commit message". More like a chain (hopefully of length one, but I canot spll wuth a dam) of the messages, git log then showing the latest of them, but allowing accessing earlier ones.

Or another way to illustrate my idea: assume a create-once-no-delete filesystem.

echo 42 > the_answr.txt
Oh, darn it...
ln -s the_answr.txt the_answer.txt

Now both names still point to the content "42\n". The first SHA would be over ["42\n", "the_answr.txt"] and the second SHA over ["42\n", "the_answer.txt"].

But I get the distinct feeling of beating a poor dead horse here, so I'll shut up.

Previous: Johannes SchindelinNext: Jeff King
Message 8 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.