[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

RE: revisions

From: Erik Hemdal <erik_at_comprehensivepower.com>
Date: Thu, 1 Oct 2009 10:45:07 -0400

The svnadmin create command establishes an empty repository.
When you did svn checkout, you created a working copy of the repository,
with no files in it (but some metadata in the .svn folders that get
Then svn commit will put the files into the repository and increment the
revision number.
You won't find readable copies of your working copy files in the repository;
what you have is the "revisions" -- the data SVN needs to be able to
reproduce any file at any specific revision. If you use ordinary tools to
make changes in the repository itself (instead of using SVN commands), you
can damage or destroy the repository. Modern versions of SVN also organize
revisions into subdirectories for efficient storage.
The SVN book describes common steps for using SVN (sometimes these are
called workflows).


To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-10-01 16:46:06 CEST

This is an archived mail posted to the Subversion Users mailing list.