This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Notes from the version control BOF at the summit
On Fri, 4 Jun 2004, Andrew Pinski wrote:
> But when we export the directories from the repository there is no
> longer this information except in the ChangeLog even someone who is
> working on their own private tree which exist only in their SCM will not
> be able figure out the history of a change unless the ChangeLog exists
> still.
That's why I think a ChangeLog is still of use. There may be a case for
such an auto-generated ChangeLog being a single log at top-level rather
than having the somewhat artificial divisions of a single change into many
logs, though this would be more tricky if the gcc and src repositories are
merged into a single new repository (there'd need to be different ways of
generating the log for each project that exclude irrelevant changes).
> Also I think a ChangeLog is a GNU code style requirement.
We can where there's a good reason decide not to follow a particular GNU
coding standard (e.g. we don't use "make dist", and don't support "make
uninstall"; the latter of these is a bit more dubious), but in this case
ChangeLogs are a good standard to keep following.
--
Joseph S. Myers
jsm@polyomino.org.uk