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

gitk bug: write commit to file takes commit message from previous commit

From
Chris Packham <judge.packham@gmail.com>
Date
Sep 3, 2014, 05:22 UTC
Message-ID
<CAFOYHZAWnaQNcCDbS3-2zxacYaD=egwhCT7qAc1DorRZ3_Pe_Q@mail.gmail.com>
Hi Paul,
Just noticed something in the version of gitk included in git 2.0.3.

When I right click on a commit and select "write commit to file" the resulting file has the diff from the selected commit but the commit message from the previous commit.

Attached is an example from running gitk on gitk (git://ozlabs.org/~paulus/gitk). As you can see the author, sha1 and diff are from 09898e7 but the message is from d4ec30b2.

I haven't tried bleeding edge gitk or bisecting yet. I'll let you know if I can track this down to a specific change.

Thanks, Chris

Next: Chris Packham
Message 1 of 2 in “gitk bug: write commit to file takes commit message from previous commit”
  1. Chris PackhamSep 3, 2014
  2. Chris PackhamSep 3, 2014

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.