Re: Editing Git Log

From: Matthias Kestenholz <mk@spinlock.ch>
Date: Sep 18, 2008, 06:21 UTC
Message-ID: <1f6632e50809172321y6343a3aau27e2ecd719185060@mail.gmail.com>
In-Reply-To: <48D1ECB4.9080808@tensilica.com>

On Thu, Sep 18, 2008 at 7:52 AM, Piet Delaney <piet.delaney@tensilica.com> wrote:

Show 14 quoted lines

> I think I recall reading that a feature of git was the prevention of the git
> commits
> from being changed. I noticed today that a couple of us have checked in
> files
> without our customary [XTENSA] architecture prefixed to the 1st line of our
> Commit Messages.
>
> I couldn't find a way to do this, other than our reverting back to a earlier
> repository
> and recommitting (each?) change with the slightly changed Commit Message;
> not an attractive investment of our time.
>
> Any suggestions?
>

You have to create new commits, but you do not have to do it by hand. See filter-branch[1]

The example given in the manpage removes the git-svn identifiers:

git filter-branch --msg-filter '
        sed -e "/^git-svn-id:/d"
'

You can probably modify the sed expression and use it nearly as is (of course you would not want to filter the whole history, only the handful commits that came from you or your team.

[1]: http://www.kernel.org/pub/software/scm/git/docs/git-filter-branch.html