MidCOM CVS Log messages like "minor change" or even "minor" etc.

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

in the past I have seen log messages like those described in the subject more
and more often.

Please, everybody, start again writing verbose precise commit logs. Even
changing a typo or adding a forgotton debug_pop() is worth mentioning in the logs.

In case you wonder why: First of all, every change should be documented. It is
absolutly worthlessly if you document that you did a change. Commit logs can
*never* be too short. Second, except from the commit list, you don't see any
patches in CVS log views. So, if you search for a change that might broke
something, you have to scan each and every minor/whatever change in CVS to
deduce wether it actually was a change that could influence you. Log overviews like

1.57 minor
1.56 minor change
1.55 updated
1.54 log

are plain useless in this respect.

Always remember that we are working in a huge software system approaching a
dozen active developers. We need every bit of documentation we can get here. I'm
not trying to harrass you with all these details, but they are a top importance
if we want to keep a certain amount of quality in the code without investing too
much time.

Please don't let it get that far as it sometimes gets with the coding convention
that I start to revert changes in CVS.


Live long and Prosper!
Torben Nehmer

- --
Torben Nehmer, Guenzburg, Bavaria, Germany
http://www.nathan-syntronics.de, mailto:[email protected]
PGP Public Key: https://www.link-m.de/pgp/t.nehmer.asc
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (MingW32)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFD6KBNJPh4Kn6d5FYRAuOyAJ9D6tGh5C7yUXcvliZNgp0dRaELLgCfUS5M
olqyY/L8TPwB62WhfNJaJM8=
=Z2e4
-----END PGP SIGNATURE-----