Re: [Flightgear-devel] Commits to FGAddon missing context

[chris <ch...@mu...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Am 03.10.2015 um 21:16 schrieb wlbragg:
>> Am I the only one that thinks commits to FGAddon should have prefixed > the plane that is being changed?

+1 !!!!!!!

I find it too frustrating, to see the logs, not knowing, which aircraft it's talking about!

I'd love to see some policy, that every commit should have it's Aircraft defined in the heading and the finer points of the commit being taken care of in the list of changes below.

Example given:

Some Aircraft:
* fictional change of FDM in a heavy manner
* changed the fiction of the viewpoint

This would be a commit-log, anyone can read sth out of it!

This is exactly the point why (for example) helijah got kicked in the butt, but it seems he didn't learn. (No offense, helijah, I got no quarrel with you, but iMHO your commit messages leave a lot to be desired!)

I firmly believe, we should make this a standard!

My 2 pennies,
chris

- -- 
http://musicchris.de

GnuPG Fingerprint: FCFF A94E E987 33C0 F9A0  3FB3 D5FC DF84 9FB3 AC75
GnuPG Info: https://musicchris.de/index.php?page=blog&index=13
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBCAAGBQJWEIAXAAoJENX834Sfs6x1cUoP/36DJo4/yeKSka4iV/XfJlkj
Dq+mT2JFLoSakFHS5mpnhcnaeAaKbu+6N6cjlnnYe/m8ry/pK9RM9dtWmwxApCWr
uSiOCxk7mbTiyPpDA+sgKZsvbCKUI7Oo65UeVPAITTSx7R/TnGm8QZ+QYTgx3D3b
Rcm9sf4NtC/2Blcnq7XuSMHu5uLK74p/B10PFDlkBtHYz/WNtFR/vi0NJrHOcla8
TXr/8pbhuSfxUREt4zYpNS4dDhWQFYdmXYw88EW71ikbpqd6Qsps7DQoWm07voec
p+S7uvLZJEA2odrmV/F+SyFo0rT+R0JIolhKFz/6FjNnFR2+/+M9PvCOhOoUL4D/
2y7/SwRR8bH/ShfZGp9PuztnC3t4hh2Le/cxC2cURrQTsDoQ+zKC0rs3pGJ3SyP8
KVXUF+4sMy+nFV42S+9Tnx8ubj4G0LA0wJ/vBtodgpuqDVo7nD4MNRFgUbvwFs7X
LwzW4bs/usHsikos2oiL0yHiNg6zRFYlsjCFwZ3e3KX1IAmE2Wg5+xwHFjXOhjha
vVni3Jizfsmsg5RDwDugmFXN/Y36d3lhwIOJKEMo7Q/utNdBQddtV3G/tm6Izfxj
LEULB+row8KkEWx2udzLFLJzQswHuvM9uMPTpV9AXj2jms9TKZvSrHdRkXCqVJY7
MQHDtdvd9WtfeDcqWb5v
=grMr
-----END PGP SIGNATURE-----