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

[Francis Dupont]

Be cool. The uniq role of the branch is to contain the patch described
in the ticket so anyway the info is to be lost if it will stay there.
Fortunately the next step is to review and merge the patch and at this
time the info will be in the master branch log and perhaps in the
Changelog too...

Regards

Francis Dupont <fdupont at isc.org>

Thomas Markwalder writes:
> Nothing is more irritating then commits with no meaningful information. 

=> my concern is more about the fact it is not possible to create
a branch with a short explanation of what the branch is for
(in fact perhaps it is possible, cf the --edit-description of git-branch?
but I never saw it to be used, and it is not of course in the procedures).