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

RE: revisions

From: vishwanath ramachandran_at_honeywell.com <ramachandran_at_honeywell.com>
Date: Thu, 1 Oct 2009 20:22:12 +0530

Erik, thanks for the reply, but my doubt is why this does not reflect in
revs folder, but in the current file its get incremented.





Desk: +91 80 26588360 Extn: 44211

Cell: +91 9008318114


From: Erik Hemdal [mailto:erik_at_comprehensivepower.com]
Sent: Thursday, October 01, 2009 8:15 PM
To: Ramachandran, Vishwanath(IE10)
Cc: users_at_subversion.tigris.org
Subject: RE: revisions




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:53:14 CEST

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