Re: cvs-commits-list reports messed up?

[Behdad Esfahbod <behdad cs toronto edu>]

On Wed, 8 Mar 2006, Behdad Esfahbod wrote:

> There has been a long discussion about this on various lists
> before.  Unless the problem is solved in the build system or
> another way, I cannot guarantee I don't do that in the future.
> That means I should never ever do 'cvs ci' and have a modified
> source tree all the time.  On the other hand, I can argue that
> it's not unnecessary.  The fact that it doesn't have new
> translation is confirmed by the fact that there's no ChangeLog
> entry for it.  The source code has changed, and the line numbers
> change.

Also note that the commit is necessary to make sure what goes in
the tarball is what is in the CVS when we tag the cvs for
release.

--behdad
http://behdad.org/

"Commandment Three says Do Not Kill, Amendment Two says Blood Will Spill"
	-- Dan Bern, "New American Language"