Subject: Re: Please stop change logs in CVS commit messages
To: None <firstname.lastname@example.org>
From: Martin J. Laubach <email@example.com>
Date: 07/11/2001 14:21:51
| Seconded. I believe that a good summary of changes for the actualy
| pkgsrc commit is quite useful.
On the other hand, finding out what exactly changed and what is
a relevant change can be quite difficult and time consuming. When I
try out a pkg, I usually check whether it is moderately recent, and
if not, update it. Here one just has to assume that newer is better,
or wade through 50k of Changelog and try to figure out what is important
and what isn't.
Even with pkgs with only minor updates (like a minor version bump
and a four line changelog) it is not obvious what is important. And
often the changelog says things like "Reworked internal-foo to be a
list instead of an array" -- WTF cares, from a pkg user perspective?