Date: Thu, 14 Apr 2016 12:50:07 +0930 From: "O'Connor, Daniel" <darius@dons.net.au> To: Ngie Cooper <yaneurabeya@gmail.com> Cc: FreeBSD Hackers <freebsd-hackers@freebsd.org> Subject: Re: Improving commit logs Message-ID: <FBAA087E-DCF3-4FB7-922D-A333AD237A23@dons.net.au> In-Reply-To: <CAGHfRMAwZ-A7BspzCqAEniyQOcy1fmL85V4wjzG0gDBq6gbjtw@mail.gmail.com> References: <56FF6534-276E-4E52-871F-5567BD9D6EC7@dons.net.au> <CAGHfRMAwZ-A7BspzCqAEniyQOcy1fmL85V4wjzG0gDBq6gbjtw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> On 14 Apr 2016, at 12:28, Ngie Cooper <yaneurabeya@gmail.com> wrote: >> Does anyone have any (constructive) comments or feedback? >=20 > Isn't this just an extension of what others have written up before? > Googling "writing good commit messages yielded: >=20 > 1. http://chris.beams.io/posts/git-commit/ > 2. = https://robots.thoughtbot.com/5-useful-tips-for-a-better-commit-message >=20 > 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". -- Daniel O'Connor "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?FBAA087E-DCF3-4FB7-922D-A333AD237A23>