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

[Eric S. R. <es...@th...>]

sfeam <sf...@us...>:
> But really I think it all looks promising. 
> Not perfect but "good enough".

I'm available to help with any dinal changes that need to be made.

I believe you big decision is whether drop the somewjat incorrect 3.7
branch - tip content doesn't match the tarballs.  I recommend dropping
it.

> Questions
> =========
> 
> 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.
-- 
		<a href="http://www.catb.org/~esr/">Eric S. Raymond</a>

My work is funded by the Internet Civil Engineering Institute: https://icei.org
Please visit their site and donate: the civilization you save might be your own.