{"thread":{"id":"15571","subject":"Editing Git Log","startedAt":"2008-09-18T05:52:52Z","lastAt":"2008-09-18T06:21:25Z","messageCount":4,"participants":["Piet Delaney","Boaz Harrosh","Matthias Kestenholz","Björn Steinbrink"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"90989","messageId":"48D1ECB4.9080808@tensilica.com","threadId":"15571","inReplyTo":null,"subject":"Editing Git Log","fromName":"Piet Delaney","fromEmail":"piet.delaney@tensilica.com","sentAt":"2008-09-18T05:52:52Z","receivedAt":"2008-09-18T05:52:52Z","isPatch":false,"sender":{"key":"piet.delaney@tensilica.com","avatar":null},"body":"I think I recall reading that a feature of git was the prevention of the \ngit commits\nfrom being changed. I noticed today that a couple of us have checked in \nfiles\nwithout our customary [XTENSA] architecture prefixed to the 1st line of our\nCommit Messages.\n\nI couldn't find a way to do this, other than our reverting back to a \nearlier repository\nand recommitting (each?) change with the slightly changed Commit Message;\nnot an attractive investment of our time.\n\nAny suggestions?\n\n-piet\n"},{"id":"90993","messageId":"48D1F19E.60907@panasas.com","threadId":"15571","inReplyTo":"48D1ECB4.9080808@tensilica.com","subject":"Re: Editing Git Log","fromName":"Boaz Harrosh","fromEmail":"bharrosh@panasas.com","sentAt":"2008-09-18T06:13:50Z","receivedAt":"2008-09-18T06:13:50Z","isPatch":false,"sender":{"key":"bharrosh@panasas.com","avatar":"https://gravatar.com/avatar/347e426f8ca0409f6891ceeefd4c3c2d8769608382323057efeaa362b4c3dbf3?d=mp&s=160"},"body":"Piet Delaney wrote:\n> I think I recall reading that a feature of git was the prevention of the \n> git commits\n> from being changed. I noticed today that a couple of us have checked in \n> files\n> without our customary [XTENSA] architecture prefixed to the 1st line of our\n> Commit Messages.\n> \n> I couldn't find a way to do this, other than our reverting back to a \n> earlier repository\n> and recommitting (each?) change with the slightly changed Commit Message;\n> not an attractive investment of our time.\n> \n> Any suggestions?\n> \n> -piet\n> --\n\ngit rebase --interactive FIRST_BAD_COMMIT^ will effectively do the same\nas above but in a nice automated way. Just change pick => edit on these\npatches that need fixing, you'll see.\n\nBoaz\n"},{"id":"90995","messageId":"20080918062116.GB32670@atjola.homenet","threadId":"15571","inReplyTo":"48D1F19E.60907@panasas.com","subject":"Re: Editing Git Log","fromName":"Björn Steinbrink","fromEmail":"b.steinbrink@gmx.de","sentAt":"2008-09-18T06:21:16Z","receivedAt":"2008-09-18T06:21:16Z","isPatch":false,"sender":{"key":"b.steinbrink@gmx.de","avatar":"https://avatars.githubusercontent.com/u/230962?v=4"},"body":"On 2008.09.18 09:13:50 +0300, Boaz Harrosh wrote:\n> Piet Delaney wrote:\n> > I think I recall reading that a feature of git was the prevention of the \n> > git commits\n> > from being changed. I noticed today that a couple of us have checked in \n> > files\n> > without our customary [XTENSA] architecture prefixed to the 1st line of our\n> > Commit Messages.\n> > \n> > I couldn't find a way to do this, other than our reverting back to a \n> > earlier repository\n> > and recommitting (each?) change with the slightly changed Commit Message;\n> > not an attractive investment of our time.\n> > \n> > Any suggestions?\n> > \n> > -piet\n> > --\n> \n> git rebase --interactive FIRST_BAD_COMMIT^ will effectively do the same\n> as above but in a nice automated way. Just change pick => edit on these\n> patches that need fixing, you'll see.\n\ngit filter-branch with a suited msg-filter is even more automated :-)\n\nBjörn\n"},{"id":"90994","messageId":"1f6632e50809172321y6343a3aau27e2ecd719185060@mail.gmail.com","threadId":"15571","inReplyTo":"48D1ECB4.9080808@tensilica.com","subject":"Re: Editing Git Log","fromName":"Matthias Kestenholz","fromEmail":"mk@spinlock.ch","sentAt":"2008-09-18T06:21:25Z","receivedAt":"2008-09-18T06:21:25Z","isPatch":false,"sender":{"key":"matthias@spinlock.ch","avatar":"https://gravatar.com/avatar/bc18f396e70163d09ab458a341b1decb7e8b6ee3aa2c0c954ec20162e67c4d46?d=mp&s=160"},"body":"On Thu, Sep 18, 2008 at 7:52 AM, Piet Delaney\n<piet.delaney@tensilica.com> wrote:\n> I think I recall reading that a feature of git was the prevention of the git\n> commits\n> from being changed. I noticed today that a couple of us have checked in\n> files\n> without our customary [XTENSA] architecture prefixed to the 1st line of our\n> Commit Messages.\n>\n> I couldn't find a way to do this, other than our reverting back to a earlier\n> repository\n> and recommitting (each?) change with the slightly changed Commit Message;\n> not an attractive investment of our time.\n>\n> Any suggestions?\n>\n\nYou have to create new commits, but you do not have to do it by hand. See\nfilter-branch[1]\n\nThe example given in the manpage removes the git-svn identifiers:\n\ngit filter-branch --msg-filter '\n        sed -e \"/^git-svn-id:/d\"\n'\n\nYou can probably modify the sed expression and use it nearly as is (of course\nyou would not want to filter the whole history, only the handful commits that\ncame from you or your team.\n\n[1]: http://www.kernel.org/pub/software/scm/git/docs/git-filter-branch.html\n"}]}