This is a fun post/article which describes the "revision" problem:
https://www.makeuseof.com/tag/file-versioning-git/ However this problem is only present in "multi-programmer" projects. As long as only one programmer is working on files for some kind of big changes, this is not a problem. Thus this article is a bit quick on to dismiss this revision technique. I can understand how something like this might get messy if everybody starts editing the same revision number etc... and put there names in front of it, and maybe messages etc. But what is the alternative ? Strange branch names ? Etc ? Some kind of description has to be given anyway. Anyway I go read that article a bit more to see if they have any solution and to see if it changes my mind. But I can already tell you: for single-programmer development, most likely no way LOL =D Bye for now, Skybuck. -- You received this message because you are subscribed to the Google Groups "Git for human beings" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/git-users/860a6c81-b939-4731-89d4-c2e92205d7b3n%40googlegroups.com.
