Page MenuHomeFreeBSD

textproc/moor: Update 2.10.4 => 2.11.0
ClosedPublic

Authored by nxjoseph on Thu, Feb 26, 7:26 PM.
Tags
None
Referenced Files
F146039160: D55540.id172788.diff
Fri, Feb 27, 6:53 AM
F146029885: D55540.id.diff
Fri, Feb 27, 4:48 AM
F146024889: D55540.id.diff
Fri, Feb 27, 3:40 AM
F146022927: D55540.diff
Fri, Feb 27, 3:13 AM
Subscribers

Details

Summary

Hi,

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

Changelogs:

Diff Detail

Repository
R11 FreeBSD ports repository
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

nxjoseph created this revision.

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

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.

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!

This revision is now accepted and ready to land.Thu, Feb 26, 7:38 PM

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.

This revision was automatically updated to reflect the committed changes.