We'll try to start providing more meaningful commit messages, but
since I've relied on the CHANGES file long before we moved to a VCS,
the muscle memory is there.
Here's what you can do though. Most of the time we make changes we
also update the CHANGES file. So most new revisions have a revised
CHANGES file. For example, go here:
I just made these tweaks. If you click on "diff" next to the CHANGES
file, you'll go here:
Scroll to the bottom and you'll see text describing the change that
was made. Hope that's sufficient.
On Dec 7, 2010, at 7:50 PM, Carlo Rossi wrote:
> I saw it and I'm a bit struggling; couldn't you at least write
> besides the "dates" the major updates (not bug fixes); or even write
> beside the versions (eg '20' ) the date when iy came up?
> --- Mer 8/12/10, Sean Luke <[log in to unmask]> ha scritto:
>> Da: Sean Luke <[log in to unmask]>
>> Oggetto: Re: updates on Google code
>> A: [log in to unmask]
>> Data: Mercoledý 8 dicembre 2010, 00:42
>> I don't usually post changes as
>> messages to SVN repository (you'll see a lot of
>> "yo"s). Instead I have traditionally modified the
>> CHANGES file on the repository to indicate the recent
>> changes. Check that out.
>> On Dec 7, 2010, at 6:00 PM, Carlo Rossi wrote:
>>> I was looking on google code and I noticed you did a
>> lot of uploads lately; is there any track about what you