textproc/moor: Update 2.10.4 => 2.11.0

[nxjoseph]

Summary

Hi,

I am updating my port textproc/moor 2 versions ahead. Thanks in advance.

Changelogs:

• https://github.com/walles/moor/releases/tag/v2.10.5
• https://github.com/walles/moor/releases/tag/v2.11.0

[osa]

I do believe it's easy and more visible to provide one line change log in the commit's message, i.e.:

ChangeLog: https://github.com/walles/moor/compare/v2.10.4...v2.11.0

[nxjoseph]

In D55540#1270842, @osa wrote:

I do believe it's easy and more visible to provide one line change log in the commit's message, i.e.:

ChangeLog: https://github.com/walles/moor/compare/v2.10.4...v2.11.0

I see, thanks for providing another way. Here's my thinking:

But it lists all the commits that happened between the versions, i.e more clutter to end user.

In release sections, mostly important commits are noted.

Thank you.

[osa]

In D55540#1270846, @nxjoseph wrote:

In D55540#1270842, @osa wrote:

I do believe it's easy and more visible to provide one line change log in the commit's message, i.e.:

ChangeLog: https://github.com/walles/moor/compare/v2.10.4...v2.11.0

I see, thanks for providing another way. Here's my thinking:

But it lists all the commits that happened between the versions, i.e more clutter to end user.

In release sections, mostly important commits are noted.

Got it, approved, thank you!

[vvd]

I usually add a link to the changelog prepared for users: Changelog, Changes, Whatisnew, Release Notes, News and etc.
"Commit log" only if there is no sensible description of the changes.