SVN negotiation with multiple VPCs
Each employee works on a copy of the same VPC and uses Tortoise to commit files. Some questions came up because all VPCs have the same hostname and commit to the same repository. Questions about whether or not this will lead to corruption or conflicts of any kind in the repository.
I originally thought this would not be a problem as commits are atomic and subversion doesn't care about the hostname of the committing machine. But I just cannot find a source that claims this as a true fact.
So the question is, are there any issues to consider when transferring files from multiple VPCs that share the same hostname?
source to share
No, it's not a problem. Records are done for every connection, so it doesn't rely on a unique host.
As an example, it is quite legal and is supported for committing to the same repository from two different directories on the same machine, at the same time, at least if they do not lead to any normal conflicts due to editing the same files, etc. .d.
source to share
This shouldn't be a problem: I often work with two different checks on the same machine and have never had a problem with it - in fact, on the project I am currently working on, we are multiple developers, some of us use multiple checks on the same machine - and no problem at all: it works exactly the same way that each of us only has one check on different machines.
SVN works on a "per commit" principle: machine, host, hostname, user, no matter ... doesn't matter.
Each commit will have a different version number and, in your case, a different username.
source to share