Re: Non-interactively rewording commit messages

From: Christian Couder <christian.couder@gmail.com>
Date: Jul 1, 2022, 11:10 UTC
Message-ID: <CAP8UFD11yVhNK0zr1A9AkTyEOHfC9fBjgZTNHDWHA0=zmJWprQ@mail.gmail.com>
In-Reply-To: <xmqqh741decp.fsf@gitster.g>

On Thu, Jun 30, 2022 at 11:35 PM Junio C Hamano <gitster@pobox.com> wrote:

>
> Christian Couder <christian.couder@gmail.com> writes:

Show 9 quoted lines

> > Have you tried `git interpret-trailers`?
>
> Do you mean a
>
>         git fast-export |
>         git interpret-trailers |
>         git fast-import
>
> pipeline?

I was thinking about using ways that are described a bit in the `git interpret-trailers` doc. And I was thinking about using ̀git rebase -i` and either adding "exec ..." lines to the todo list (possibly with `--exec ...` ) or maybe using "reword ..."

About ways that are described in the `git interpret-trailers` doc, there is:

* the following example with `git format-patch`:

      •   Extract the last commit as a patch, and add a Cc and a
Reviewed-by trailer to it:

              $ git format-patch -1
              0001-foo.patch
              $ git interpret-trailers --trailer 'Cc: Alice
<alice@example.com>' --trailer 'Reviewed-by: Bob <bob@example.com>'
0001-foo.patch >0001-bar.patch

* the example with a commit-msg hook that uses git interpret-trailers

BTW using interpret-trailers' --in-place option might be better than handling files the way it's done in both these examples.