On Friday, March 4, 2022 at 8:23:58 AM UTC+1 skybuck2000 wrote:
> This is a fun post/article which describes the "revision" problem: > > https://www.makeuseof.com/tag/file-versioning-git/ > > > Read a bit further into it. What I could do is rename the versioned files back to the original. So example: module.txt module_version1.txt module_version2.txt module_version3.txt When I am done with module_version4.txt I could rename it back to module.txt But ofcourse do you seem the problem ? This kinda feels akward and might make more confusion then it's worth it... then again maybe not if looking at the files in a timeline... Deleting v1,2,v3 is very much undesireable. So this is a very clear situation where GIT is now fighting and in conflict with existing versioning information. Basically once files are versioned as described above GIT becomes useless or confusing at best, hence a solution should be made/found for this to make GIT interoperable with versioning systems as described above. The completely lack/loss of versioning information in most projects on github/git repos is kind of concerning it gives a lack of sense of much change a file has experienced. There is very little indication except for the lastest timestamp... but this could also be misleading. Currently at best what I have seen is a "linux rc6" or a "pascal coin release tag 5.4" this is then some tag slammed onto all files at the project at large. Fine-grained per file versioning information and change velocity is completely lost it seems, quite a shame in a way. 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/0a9bf0a8-9899-4bb9-98ef-0244aab86eben%40googlegroups.com.
