{"thread":{"id":"37476","subject":"gitk bug: write commit to file takes commit message from previous commit","startedAt":"2014-09-03T05:22:46Z","lastAt":"2014-09-03T05:47:39Z","messageCount":2,"participants":["Chris Packham"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"248770","messageId":"CAFOYHZAWnaQNcCDbS3-2zxacYaD=egwhCT7qAc1DorRZ3_Pe_Q@mail.gmail.com","threadId":"37476","inReplyTo":null,"subject":"gitk bug: write commit to file takes commit message from previous commit","fromName":"Chris Packham","fromEmail":"judge.packham@gmail.com","sentAt":"2014-09-03T05:22:46Z","receivedAt":"2014-09-03T05:22:46Z","isPatch":false,"sender":{"key":"judge.packham@gmail.com","avatar":"https://avatars.githubusercontent.com/u/155667?v=4"},"body":"Hi Paul,\n\nJust noticed something in the version of gitk included in git 2.0.3.\n\nWhen I right click on a commit and select \"write commit to file\" the\nresulting file has the diff from the selected commit but the commit\nmessage from the previous commit.\n\nAttached is an example from running gitk on gitk\n(git://ozlabs.org/~paulus/gitk). As you can see the author, sha1 and\ndiff are from 09898e7 but the message is from d4ec30b2.\n\nI haven't tried bleeding edge gitk or bisecting yet. I'll let you know\nif I can track this down to a specific change.\n\nThanks,\nChris\n"},{"id":"248771","messageId":"CAFOYHZDtaLEcdOSGA8h99rDTUzsn9z7JytgFLi-WGzZ525QkvQ@mail.gmail.com","threadId":"37476","inReplyTo":"CAFOYHZAWnaQNcCDbS3-2zxacYaD=egwhCT7qAc1DorRZ3_Pe_Q@mail.gmail.com","subject":"Re: gitk bug: write commit to file takes commit message from previous commit","fromName":"Chris Packham","fromEmail":"judge.packham@gmail.com","sentAt":"2014-09-03T05:47:39Z","receivedAt":"2014-09-03T05:47:39Z","isPatch":false,"sender":{"key":"judge.packham@gmail.com","avatar":"https://avatars.githubusercontent.com/u/155667?v=4"},"body":"On Wed, Sep 3, 2014 at 5:22 PM, Chris Packham <judge.packham@gmail.com> wrote:\n> Hi Paul,\n>\n> Just noticed something in the version of gitk included in git 2.0.3.\n>\n> When I right click on a commit and select \"write commit to file\" the\n> resulting file has the diff from the selected commit but the commit\n> message from the previous commit.\n>\n> Attached is an example from running gitk on gitk\n> (git://ozlabs.org/~paulus/gitk). As you can see the author, sha1 and\n> diff are from 09898e7 but the message is from d4ec30b2.\n>\n> I haven't tried bleeding edge gitk or bisecting yet. I'll let you know\n> if I can track this down to a specific change.\n\nActually I don't think it's a gitk problem. If I run\n\n  git diff-tree --stdin -p --pretty << EOF | less\n  09898e7c3b040086e8addd4ef226548c9dce1460\n  EOF\n\nI get the wrong commit message. Looking at the release notes this has\nalready been fixed in 2.0.4. Sorry for the noise.\n"}]}