> 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?
Also, even short messages like, "Added \foo command", or "Fixed \bar alignment" would probably be helpful. 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. Gr. Matthijs
signature.asc
Description: Digital signature
___________________________________________________________________________________ If your question is of interest to others as well, please add an entry to the Wiki! maillist : [email protected] / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://tex.aanhet.net archive : https://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___________________________________________________________________________________
