This is the mail archive of the mailing list for the glibc project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: ChangeLog entry complexity

> > There was some good discussion recently on a Google+ thread I started
> > regarding the tradition of writing detailed change notes.
> > 
> >
> > 
> > Does anyone feel strongly that detailed change logs are limiting our
> > acceptance of new developers to the community?
>   I think writing detailed change logs is absolutely great. For example,
> browsing the history of the Git version control system or (mostly) the
> Linux kernel is quite pleasurable and you have a good chance of learning
> the complete background and all else you need to know about a change
> from the Git history.
>   But that is very different from the ChangeLogs, which just describe
> *what* has been changed in great detail, something quite obvious from
> the diffs themselves.

Exactly my thoughts.

Also having ChangeLogs in files under git source control polutes diffs
between versions with metadata that really should have been in the git
logs instead.

Detailed descriptions of changes are great ChangeLogs files are just
wrong place to put them.

Cyril Hrubis

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]