Menu
For example when working from computers which have different git software versions installed.
931
Probably the easiest way is create branches for each version and then do for example git checkout v1. 0.14 or whatever branch you want to work on. The clients can then also check out the appropriate branch for the one they need as well as when upgrading to next version.
Git is an open source distributed version control system that helps software teams create projects of all sizes with efficiency, speed, and asynchronicity.
Generated files can bloat the version control history (the size of the database that is stored in the repository). A small change to a source file may result in a rather different generated file.
A centralized version control system only has two data repositories that users have to monitor: the local copy and the central server. Distributed version control systems, like Git, use multiple repositories, which can decrease insight into projects.
git's repository layout has been very stable over time, so using even very old versions of the software with repositories created by later versions should work fine. Of course, there may be config options set by later versions that aren't understood by earlier versions of the tools, but this should not cause problems except perhaps that the older software doesn't behave as you would expect.
Also, it should be fine to use versions of the tools built for different operating systems on the same on-disk repository.
There are particular features, such as submodules, that may not be supported by older versions of git - to be able to assess whether that would be a problem you would have to tell us what the oldest version you might be using is.
You might also want to look at this question about git's backwards-compatibility:
78
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
