Matthijs Kooijman wrote:
well, such messages would not help much unless they would be detailed (and then should be done for each file); as i work on all files at the same time it would cost me way to much time and it gains me nothing; looking at the diff in a git gui is more informative A git commit contains changes to multiple files, with a single message, so if you work on one logical change at a time, this should not be a problem. Perhaps you are thinking of CVS, which (AFAIK) provides only per-file versioning?
sure, but i never change 'one file' per commit, often many small changes in files (even typos or just formatting)
Also, even short messages like, "Added \foo command", or "Fixed \bar alignment" would probably be helpful.
i've probably forgotten that by the time i submit a zip as there can be quit esome time between a commit then
Then again, you are completely correct that there is some effort to be invested to properly use a versioning system, especially if you're not used to working with one. In my experience, having a versioning system like git (or mercurial seems to be good as well) does pay off in the long run, but only if you tune your development flow to work well with it.
indeed, and we started on context way before there was git (and many files are involved, not only tex files); changing now would probably stall me for a while Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------