# Editing git changelog automatically 6 messages from 2014-10-27 to 2014-10-30. Participants: Cong Wang, Dennis Kaarsemaker, Matthieu Moy, Andreas Schwab. Thread: https://gitlist.dev/t/37818 ## Cong Wang, 2014-10-27 05:27 Subject: Editing git changelog automatically Message-ID: URL: https://gitlist.dev/e/CAM_iQpWNQbv_GTT%2BH5KNCqqRS3qWfBuBge4%2BZTAS_WiaREku4w%40mail.gmail.com ``` Hello, git experts Sorry if this is a question already answered, but google search didn't give me anything useful. My question is how to edit dozens of git commit changelogs automatically? Let's say I want to fix a stupid typo in all of these commits, as simply as s/foo/bar/. Usually I use`git rebase -i` and `git commit --amend`, but both of them are interactive, apparently I don't want to edit them one by one. :) I know I can change $EDITOR to something like `sed -e 's/foo/bar/'`, but this seems pretty ugly. Is there a clean way to do that? Thanks! ``` ## Dennis Kaarsemaker, 2014-10-27 06:05 Subject: Re: Editing git changelog automatically Message-ID: <1414389944.7883.2.camel@spirit> URL: https://gitlist.dev/e/1414389944.7883.2.camel%40spirit In-Reply-To: ``` On zo, 2014-10-26 at 22:27 -0700, Cong Wang wrote: > > My question is how to edit dozens of git commit changelogs > automatically? You can use git filter-branch in --msg-filter mode. -- Dennis Kaarsemaker www.kaarsemaker.net ``` ## Matthieu Moy, 2014-10-27 08:33 Subject: Re: Editing git changelog automatically Message-ID: URL: https://gitlist.dev/e/vpq38a9lxnu.fsf%40anie.imag.fr In-Reply-To: <1414389944.7883.2.camel@spirit> ``` Dennis Kaarsemaker writes: > On zo, 2014-10-26 at 22:27 -0700, Cong Wang wrote: >> >> My question is how to edit dozens of git commit changelogs >> automatically? > > You can use git filter-branch in --msg-filter mode. Note that in any case, you'll rewrite the history hence change commit identifiers. If the history is already published, it's probably better to live with the typo than to try to fix it now. -- Matthieu Moy http://www-verimag.imag.fr/~moy/ ``` ## Andreas Schwab, 2014-10-27 18:58 Subject: Re: Editing git changelog automatically Message-ID: <87zjch9w5w.fsf@igel.home> URL: https://gitlist.dev/e/87zjch9w5w.fsf%40igel.home In-Reply-To: ``` Cong Wang writes: > Let's say I want to fix a stupid typo in all of these commits, as > simply as s/foo/bar/. Usually I use`git rebase -i` and `git commit > --amend`, but both of them are interactive, apparently I don't want to > edit them one by one. :) Both can be scripted, though. > I know I can change $EDITOR to something like `sed -e 's/foo/bar/'`, > but this seems pretty ugly. Is there a clean way to do that? I don't see the ugliness. There is no requirement that $EDITOR is interactive. Andreas. -- Andreas Schwab, schwab@linux-m68k.org GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5 "And now for something completely different." ``` ## Cong Wang, 2014-10-30 06:13 Subject: Re: Editing git changelog automatically Message-ID: URL: https://gitlist.dev/e/CAM_iQpWAHtTOXsiGPbQOMs4x9VBMaFOXMUYaSZi4V1aFrvTgUg%40mail.gmail.com In-Reply-To: <1414389944.7883.2.camel@spirit> ``` On Sun, Oct 26, 2014 at 11:05 PM, Dennis Kaarsemaker wrote: > On zo, 2014-10-26 at 22:27 -0700, Cong Wang wrote: >> >> My question is how to edit dozens of git commit changelogs >> automatically? > > You can use git filter-branch in --msg-filter mode. This is exactly what I am looking for. Good to know this git command. Thanks! ``` ## Cong Wang, 2014-10-30 06:14 Subject: Re: Editing git changelog automatically Message-ID: URL: https://gitlist.dev/e/CAM_iQpW-_src0W2-WkDRTMobua6UAQncvPqcxfqi6T82TdC7eA%40mail.gmail.com In-Reply-To: ``` On Mon, Oct 27, 2014 at 1:33 AM, Matthieu Moy wrote: > Dennis Kaarsemaker writes: > >> On zo, 2014-10-26 at 22:27 -0700, Cong Wang wrote: >>> >>> My question is how to edit dozens of git commit changelogs >>> automatically? >> >> You can use git filter-branch in --msg-filter mode. > > Note that in any case, you'll rewrite the history hence change commit > identifiers. If the history is already published, it's probably better > to live with the typo than to try to fix it now. I am aware of that, it is my local branch, so no worry. Thanks. ```