Just compare and see what’s easier for you. Ultimately Git was developed by developers for developers. If you just need version control for yourself and maybe a few others without the need to install servers or putting your code out on a public server, VersionRecall is a better solution. If you need to collaborate with multiple team members and you have a place to host a Git server (public or private) you should examine if it is right for you. Question: I was considering using Git, why would I use VersionRecall instead?Īnswer: Git works well as a distributed version control system. Managing versions and dealing with things under the hood is what this product aims to avoid, so we submit in intervals, at fixed times or on demand but not each time a file changes. Creating a new version each and every time a file changes creates many versions of a file, which in turn requires you to weed out the unwanted versions at some point. Question: Why do you not just submit a file each time it is modified?Īnswer: While developing scripts, most people frequently save and run to verify that what they have done so far works. Here is a list of the most common ones and the answers to them. Over the course of the weeks since the release of VersionRecall 2014 we have received a number of questions.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |