| 1 |
On Wed, 23 May 2012 12:29:34 -0400 |
| 2 |
Rich Freeman <rich0@g.o> wrote: |
| 3 |
|
| 4 |
> On Wed, May 23, 2012 at 4:02 AM, Samuli Suominen |
| 5 |
> <ssuominen@g.o> wrote: |
| 6 |
> > On 05/23/2012 05:36 AM, Ryan Hill wrote: |
| 7 |
> >> One person doesn't do entries. OMG let's remove it! |
| 8 |
> >> |
| 9 |
> > |
| 10 |
> > absolutely because inconsitency renderess the file useless |
| 11 |
> > |
| 12 |
> |
| 13 |
> Well, for now the solution is to enforce following policy. |
| 14 |
> |
| 15 |
> For the future, perhaps the policy's time has ended. Sure, Changelogs |
| 16 |
> can be handy, but they are increasingly redundant and scm comments |
| 17 |
> have the potential to be far more useful. By all means require |
| 18 |
> meaningful scm commit comments, but if Changelog files are holding us |
| 19 |
> back either auto-generate them or ditch them. |
| 20 |
|
| 21 |
ChangeLogs could be fine for ebuilds. But for more broad cases like |
| 22 |
eclasses, one can usually have a set of changes prepared for commit. |
| 23 |
With CVS, it's PITA but with git it's already much better. Of course, |
| 24 |
it all fails if every commit has to update a randomly changed, shared |
| 25 |
file called ChangeLog... |
| 26 |
|
| 27 |
-- |
| 28 |
Best regards, |
| 29 |
Michał Górny |
Archives