Because of security restrictions, I have an environment with 2 Windows PCs which are basically air-gapped - ie not connected to any network.
Both PCs will develop some code, which is a shared development between them. The only mechanism for sharing this between the 2 PCs is via an encrypted external drive, which will only be used for that purpose.
I want to have some form of version control which will allow the version-controlled files/VC archives to be exchanged between the machines so that each machine can work on any part of the shared code base.
I can accept limitations that we will have to "manually" avoid working on the same code (the machines/users are co-located), as the VC software won't have any knowledge of locks / changes happening on the other machine
What are my options? GIT looks like it might work for this, treating the external drive as the master repository, and I could live with that though I'm not a great fan of, nor very experienced with, GIT (all my VC history is with PCVS (mostly) and SCCS). Is there anything better/simpler than GIT that would work in this scenario?