Does the svn 1.7 working copy format store the entire history of the repo?

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?

  • Are users able to find my e-mail / name via commits on github using API?
  • How can I commit a file to SVN that I forgot to commit a while ago, (tweaking it's revision number)
  • xcode commit missing file or directory
  • how to get partial update from subversion
  • Rolling back bad changes with svn in Eclipse
  • SVN permissions for a single file
  • Branch vs. Tag vs. Revision in SVN terminology
  • Import svn into git
  • svn: replace trunk with branch
  • git svn command crashes in the middle of cloning svn repo. How to fix that?
  • Release management in SVN
  • SVN installation
  • 2 Solutions collect form web for “Does the svn 1.7 working copy format store the entire history of the repo?”

    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).

    No, the .svn directory keeps a pristine version of what you’ve checked out of the repository. (i.e. the BASE revision) It does not keep all the history.

    SVN does not work disconnected. You need to have a connection to the server, unless of course you’ve checked out your working copy from a URL like file:///c:/my_dir — which is to say you’re working with a local repository.

    Git Baby is a git and github fan, let's start git clone.