Menu
To access our SVN repository I'm using git svn and other team members are using svn.
When they set the needs-lock property it appears that git svn ignores this and allows me to update the files anyway.
Is that accurate?
Also, is it possible to manage the needs-lock property using git svn?
364
Git allows you to modify previous commits and changes using tools like git rebase . GitHub supports Subversion clients, which may produce some unexpected results if you're using both Git and SVN on the same project. If you've manipulated Git's commit history, those same commits will always remain within SVN's history.
If you Get a Lock on a file, then only you can commit that file. Commits by all other users will be blocked until you release the lock. A locked file cannot be modified in any way in the repository, so it cannot be deleted or renamed either, except by the lock owner.
The difference between Git and SVN version control systems is that Git is a distributed version control system, whereas SVN is a centralized version control system. Git uses multiple repositories including a centralized repository and server, as well as some local repositories.
From git-svn documentation under bugs:
We ignore all SVN properties except svn:executable. Any unhandled properties are logged to $GIT_DIR/svn//unhandled.log
And since svn:needs-lock is a communication to the client saying that the file had to be made read only, you cannot achieve this with git-svn.
169
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
