3 ms·
Your scheme could conflict if 2 people have version 8 and create a version 9. You may think, I know I’ll use a time stamp! But the file system already keeps tra
by twobitshifter 5y ago
Your scheme could conflict if 2 people have version 8 and create a version 9. You may think, I know I’ll use a time stamp! But the file system already keeps track of the file modified time, so why encode it in the filename?
For file versioning in business without collaborative editing, you can keep the same filename and use check-in and checkout scheme, with a revision history.
For working by yourself and keeping track of the file, the windows and Mac file systems will also keep a copy of previous versions that you can restore so keeping around the copies as separate files has no benefit.
https://support.apple.com/guide/mac-help/view-and-restore-past-versions-of-documents-mh40710/mac https://support.apple.com/guide/mac-help/view-and-restore-pa...
https://www.minitool.com/news/enable-previous-versions-windows-10.html https://www.minitool.com/news/enable-previous-versions-windo...
- ttoinou 5y agoYeah I was thinking out of git stuff obviously. And not collaborative, it's even more complex there. I didn't know about that for Mac ! Interesting thanks. For Windows it's a backup thing, not something you'd use everyday. In any case it's practical to have all version of the files to see how it is progressing so far, not having to do complex operations to get back a previous file Using timestamps is also not very practical, would you say "please revert back the change on the file from Feb 13 11h23" ?
- twobitshifter 5y agoFor the check in check out, that’s not git but more like Sharepoint or any other document management system.