Jim Meyering wrote: > I've been thinking about this for years, ever since the unpleasantness > of that first git commit that I mistakenly attributed to myself. > > With this new --amend=FILE option, you'll be able to maintain > a list of <SHA,CODE+> pairs where SHA is a 40-byte SHA1 > (alone on a line) referring to a commit in the current project, and > CODE refers to one or more consecutive lines of Perl code. > Pairs must be separated by one or more blank lines. > Using that file, invoke gitlog-to-changelog with this new option, > and it'll do the rest. > > Here's the one I expect to use for coreutils: > > --------------------------------------------------------- > # This file is expected to be used via gitlog-to-changelog's --amend=FILE > # option. It specifies what changes to make to each given SHA1's commit > # log and metadata, using Perl-eval'able expressions. > > 3a169f4c5d9159283548178668d2fae6fced3030 > # fix title: > s/all tile types/all file types/ > > e181802521d4e19e367dbe8cfa877296bb5dafb2 > # fix the title! > s,seq:,factor:, > > 3ece0355d52e41a1b079c0c46477a32250278c11 > # correct the URL > s,<[^>]+>,<http://bugs.debian.org/412688>,
Oops. I corrected that at the last minute and forgot to update. It should be: s,<http.+?>,<http://bugs.debian.org/412688>, Otherwise, it'll mistakenly change my <email address> on the first line to that URL.
