Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I’m curious about the capabilities of the new working copy format in Subversion 1.7 (the single .svn directory at the root).
Does it store an entire history of the repo, like git does? Or are the files in pristine merely a copy of the current (unedited) revision from the server? Does svn support working disconnected at all – committing multiple times locally before pushing to the server?
Subversion only maintains the revision you currently have checked out locally. (Some meta data about other revisions might be cached depending on your client, but the actual file content from other revisions will not be stored.)
There’s no way to commit other than committing to the actual repository. Just a design difference of git vs subversion (centralized vs distributed).