On 10 Sep, Mark Taylor wrote:
> Changing them makes life very difficult for people (like myself) who
> try to keep up with *important* changes. When the MP3 output has
> changed, it is usefull to track down why it has changed, and thus code
> changes (which do not represent bug fixes or additional functionality)
> should be kept to a minimum.
Why don't you establish some rules:
- "Don't mix style and content commits. Never."
- "You have to mark every style commit in the cvs commit message with
�your prefered 'tag' for a style commit�."
This would:
- improve the readability/consistency of the code
- makes your life not very difficult for this sorts of commits
Just my 0.02 EUR,
Alexander.
--
There's no place like ~
http://www.Leidinger.net Alexander @ Leidinger.net
GPG fingerprint = 7423 F3E6 3A7E B334 A9CC B10A 1F5F 130A A638 6E7E
--
MP3 ENCODER mailing list ( http://geek.rcc.se/mp3encoder/ )
