Style Commit policy

[Neil Stevens]

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

On Thursday September 19, 2002 01:44, Stephan Binner wrote:
> On Thursday 19 September 2002 10:31, Neil Stevens wrote:
> > When you make commits with your stock log message, are you just
> > changing capitalization, then?  The style guide addresses a lot more
> > than just that
>
> No, most recent ones fixed trailing ellipsis. And the next run will
> contain things such as "K Address Book"->KAddressbook". I'm willing to
> use described script but will not classify every file commit while
> doubling my efforts just because someone interested is unwilling to
> click on a provided link.

OK, but all the changes are just to strings?  You're not changing click 
behaviors or changing MDI apps to SDI or anything?  At least change the 
log message to reflect that you're only changing strings, then.  As Harri 
points out, changing strings is innocuous compared with what your log 
implies you might be doing.

Ideally, you'd change your log message once per "run" to describe what that 
run is doing.  Unlike Skript Kiddy's "made messages" which is just doing 
the same routine every day, your changes are different every time.

thanks,

- -- 
Neil Stevens - neil at qualityassistant.com
"I always cheer up immensely if an attack is particularly wounding
because I think, well, if they attack one personally, it means they
have not a single political argument left." - Margaret Thatcher
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE9iZBuf7mnligQOmERApNCAJ9v08HSBfPdmKNl5PcEQ2ULi8S48ACdENR6
5jB+mJzs+6lbHgmUWJBl1mk=
=LQxe
-----END PGP SIGNATURE-----