Re: Status update - version 5.2.2, cvs->git conversion, plans

[Dima K. <gn...@di...>]

Eric S. Raymond <es...@th...> writes:

> sfeam <sf...@us...>:
>
>> I'm still learning how to rethink my work flow for git, so please
>> help me out.   For instance, does it make any sense to continue
>> to maintain the ChangeLog file?   So far I'm having little success in
>> keeping it in sync with the git commit messages.  Is there some
>> tool to help with that, or is the normal practice with git to rely
>> only on the commit messages? I know you can dump a log of commits,
>> so I guess one possibility is to use that to update the ChangeLog every
>> now and then (1 month intervals? 6 months?) but not try to touch it
>> for every commit.  Advice?
>
> I recommend no longer keeping a ChangeLog.  In fact. I recommend deleting it
> from the tip version.  It will, of course, still be available to anyone
> who cares to check out the last pre-conversion revision.
>
> In the presence of changeset comments with author attributions. Changelog
> comments are duplicative and the requirement to do them becomes increasingly
> annoying.  Better to write changeset comments and browse those with
> gitk or equivalent.

Agreed. My feeling is that you want some sort of NEWS file that
describes a very high-level list of changes so that somebody can clearly
see the big differences between releases. But for finer-grained stuff,
the version control should be the master record.