-----BEGIN PGP SIGNED MESSAGE-----
On 05/23/2012 05:46 PM, Michał Górny wrote:
> On Wed, 23 May 2012 12:29:34 -0400 Rich Freeman <firstname.lastname@example.org>
>> On Wed, May 23, 2012 at 4:02 AM, Samuli Suominen
>> <email@example.com> wrote:
>>> On 05/23/2012 05:36 AM, Ryan Hill wrote:
>>>> One person doesn't do entries. OMG let's remove it!
>>> absolutely because inconsitency renderess the file useless
>> Well, for now the solution is to enforce following policy.
>> For the future, perhaps the policy's time has ended. Sure,
>> Changelogs can be handy, but they are increasingly redundant and
>> scm comments have the potential to be far more useful. By all
>> means require meaningful scm commit comments, but if Changelog
>> files are holding us back either auto-generate them or ditch
> ChangeLogs could be fine for ebuilds. But for more broad cases
> like eclasses, one can usually have a set of changes prepared for
> commit. With CVS, it's PITA but with git it's already much better.
> Of course, it all fails if every commit has to update a randomly
> changed, shared file called ChangeLog...
So we did we introduce changelogs for eclass/ in the first place if
everyone is happy with getting rid of them?
Markos Chandras / Gentoo Linux Developer / Key ID: B4AFF2C2
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
-----END PGP SIGNATURE-----