On 31/10/2021 05:14, skybuck2000 wrote: > My own versioning system is very simple and used for solo development > 99.99999%. > > I will give an example of how this works. > > The main thing is "folders", "version number in folders" and "comments > in folders". > > For example, let's suppose I want to test an algorithm called "Jack". > > I would create a folder like so: > > C:\Source Code\Tests\Test Jack\version 0.01 original code\ > > Then I would make a copy of that code: > > C:\Source Code\Tests\Test Jack\version 0.02 modify it\
I and a colleague had a versioning system like that. We zip compressed the top level directory to keep the backup (had the version number). I was better than trying to use the corporate system (too many 'controls') of either a 'big-iron' system or SVN (I never used). After completion I created a Git repo by simply extracting each snapshot (I have a script somewhere) and then overlaying the previous versions as the Git repo built. At least it gives a better overview, though the diffs can be terrible. Git is especially good in collaborative work, without some top knob being in 'control'. The hash is simple and unique and avoids all the coordination issues. > version numbers in file names are not that usefull for application code, there are however very usefull for shared code between applications, so that applications can always be build against exact version numbers. > This is what worries me the most for GIT, it's not suited for shared files between applications, updating code in a "working folder" would be horrible and break every application that ever used it, here versioning in folder names and file names is far superior to always be able to build ANYTHING at ANYTIME. This is a 'mental model' misunderstanding. It is a 'kit of parts / parts catalog' viewpoint (home built vehicle), while Git's primary view is that of 'the project' (compare to having a make/model of a car). In Git you would designate each of the resuable folder/files as a sub-module, which can then be integrated when/wherever it's needed by a major project. The (supra-)project choses the version that is used. (I've not read everything so I may have missed stuff) -- Philip -- 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/63e93ed7-d74d-5988-4502-0472068f2b34%40iee.email.
