commit IDs in changelog messsages

Manoj Srivastava srivasta at
Sun Nov 16 16:44:02 UTC 2008

On Sat, Nov 15 2008, martin f krafft wrote:

> also sprach Manoj Srivastava <srivasta at> [2008.11.14.0719 +0100]:
>>   f) edit ./debian/changelog, adding in any additional language. I
>>      generally keep my commit messages and changlog entries distinct,
>>      since commit messages explain the code changes to a developer, and
>>      changelogs are geared towards the end user.
> This is why Git allows you to write essays in addition to the short
> commit summary, which should always be geared to everyone.

        You did not miss the previous step:
>>  e) dch --no-auto-nmu --append --  \ 
>>       $(git log --abbrev-commit --pretty=oneline HEAD\^.. | \
>>            perl -pli -e 's/\.\.\.//;' -e 's/\s*(\S+) /[$1] /')
>>     This adds a line into ./debian/changelog

        If you missed it, this does provide the commit summary line into
 the changelog. It also works whether I am in the integration branch, or
 in the ./debian submodule, which is a required feature for me (I can't
 use git-dch, because it assumes that ,.debian lives in the integration

        I think that the body of the commit log is always people working
 on the code; the Changelog is for people using apt-listchanges or
 loking at /usr/share/doc/foo/ ;, and is geared more towards user
 visible changes.

One of the most overlooked advantages to computers is...  If they do
foul up, there's no law against whacking them around a little.  -- Joe
Manoj Srivastava <srivasta at> <>  
1024D/BF24424C print 4966 F272 D093 B493 410B  924B 21BA DABB BF24 424C

More information about the vcs-pkg-discuss mailing list