Improving commit logs

[Ngie Cooper]

On Wed, Apr 13, 2016 at 8:28 PM, Glen Barber <gjb at freebsd.org> wrote:
> On Thu, Apr 14, 2016 at 12:50:07PM +0930, O'Connor, Daniel wrote:
>>
>> > On 14 Apr 2016, at 12:28, Ngie Cooper <yaneurabeya at gmail.com> wrote:
>> >> Does anyone have any (constructive) comments or feedback?
>> >
>> > Isn't this just an extension of what others have written up before?
>> > Googling "writing good commit messages yielded:
>> >
>> > 1. http://chris.beams.io/posts/git-commit/
>> > 2. https://robots.thoughtbot.com/5-useful-tips-for-a-better-commit-message
>> >
>> > This is what I generally try to follow with commits...
>>
>> Sure, but I think it carries more weight if you can point to a
>> specific FreeBSD document and say "do it like this".
>>
>
> As one of the people that has to suffer through delving through commit
> logs to find the 'gems', I can personally guarantee that documenting
> "how to write good commit messages" will be less than fruitful.

Good point: usefulness is in the eye of the beholder. What's good for
me to know might be completely irrelevant for someone else.. I guess
this is where it helps to get CRs from people who aren't SMEs in the
area that you need feedback with..
-Ngie