[kea-dev] missing commit details (was Re: [Kea-changes] KEA trac3824, updated. 7697c53c441338748fd678e10c3b38384f379ef6 [3824] #3824 patches)

[Thomas Markwalder]

On 5/12/15 7:25 AM, Jeremy C. Reed wrote:
> On Tue, 12 May 2015, kea-dev at lists.isc.org wrote:
>
>>     [3824] #3824 patches
> I saw multiple branches with similar commit log messages. Please 
> consider some details in future. (I cannot find in the instructions for 
> this in the trac wiki.)
> _______________________________________________
> kea-dev mailing list
> kea-dev at lists.isc.org
> https://lists.isc.org/mailman/listinfo/kea-dev
Nothing is more irritating then commits with no meaningful information. 
Having to go to Trac just to see what a change relates to is
unacceptable in my view.   If someone is trying to chase down the source
of an issue, what goes into the commit log needs to be enough to at
least give them a clue.  Additionally,  Trac may not always be
accessible.  Suppose someone is working on a plane?   What if 10 years
from now we've moved off Trac and the issue is lost or cannot be found?