Re: ChangeLogs in commit messages

Doug Evans <[email protected]>
Newsgroups gmane.comp.gdb.devel
Message-ID <CADPb22QNmq96=QDs-Da086XTsDpkJsiet_fYsHT0mkRoF+VkfQ@mail.gmail.com>
On Tue, Sep 9, 2014 at 1:51 AM, James Hogan <[email protected]> wrote:
> On 08/09/14 14:24, Joel Brobecker wrote:
>>> IMHO this is a really bad idea.
>>
>> I wouldn't say "a really bad", but I tend to agree with the reasoning.
>> It's a bit unnatural to me that git would chose to show the author
>> date by default over the commit date
>
> From the patch author point of view, cleaning up a patchset by
> interactive rebasing, or rebasing to keep their branch up to date, I
> think the author date probably is more natural, and in less linear
> histories (look at Linux repo for example) I suspect the commit date
> wouldn't be as meaningful.

Authors come and go, and, for me as an author, after six months I
would certainly prefer to see in the upstream tree a date as close as
possible to when the patch was pushed upstream.
[plus the needs of the many outweigh the needs of the few ... 1/2 :-)]

> [...] It'd be nice if
> something similar was possible with git-blame.

Indeed!

> You can add new pretty formats too, e.g.
>
> [pretty]
>         fullcommit = "commit %H\nAuthor:     %an <%ae>\nCommitDate: %cd\n\n%B"
> [format]
>         pretty=fullcommit
>
> This shows author name, but commit date, but I didn't figure out how to
> indent the body like pretty=fuller does.

Interesting, thanks!
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.