when run in repos other than gcc mklog fails to find ChangeLog files
because it looks for $0/../$dir/ChangeLog, but of course if the diff is
for a project other than gcc that might not exist. It should be fine to
also look for $cwd/$dir/ChangeLog, and use that if we find it. This
means that for example in binutils-gdb.git you can do git commit,
and then in your editor read git diff HEAD~ | mklog - to generate a
template ChangeLog for that commit.
contrib/ChangeLog:
2016-03-06 Trevor Saunders <tbsaunde+gcc@tbsaunde.org>
* mklog: Look for the ChangeLog file in $cwd.
From-SVN: r234014
2014-11-25 Tom de Vries <tom@codesourcery.com>
Peter Bergner <bergner@vnet.ibm.com>
* mklog: Handle .mklog. Use git setting independent of presence .git
directory.
Co-Authored-By: Peter Bergner <bergner@vnet.ibm.com>
From-SVN: r218050
2014-11-14 Tom de Vries <tom@codesourcery.com>
* mklog: Move reading of .diff file up and add comment. Copy diff_lines
to orig_diff_lines. Use orig_diff_lines when appending patch.
From-SVN: r217558
The new mklog script prints three spaces after the date part, which
is wrong. Thus fixed by adjusting the split pattern. Tested manually.
2012-05-31 Marek Polacek <polacek@redhat.com>
* mklog: Prevent printing three spaces after the date.
From-SVN: r188265
This script analyzes a .diff file and generates a skeleton ChangeLog
entry for it. It tries fairly hard to find function names, so it's
important to use the -p switch with diff.
I wrote the initial code a while ago. Cary added a bunch of smarts to
make it understand C++ and guess the function names better than the
original version.
2012-05-31 Diego Novillo <dnovillo@google.com>
Cary Coutant <ccoutant@google.com>
* mklog: New.
Co-Authored-By: Cary Coutant <ccoutant@google.com>
From-SVN: r188072
