[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 11:11:55 -0400

-----Original Message-----
From: vishwanath ramachandran_at_honeywell.com
[mailto:vishwanath.ramachandran_at_honeywell.com]
Sent: Thursday, October 01, 2009 10:52 AM
To: Erik Hemdal
Cc: users_at_subversion.tigris.org
Subject: RE: revisions

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.

 

 

That's because

 

/server/directory/containing/repository-name/db/revs/0

 

is a directory containing files of data which SVN uses to manage your
versioned files. These are not complete copies of files you store in the
repository, in general.

 

You cannot go into the repository using shell commands to get copies of your
versioned files. You must use SVN commands or the SVN API to do that. Use
either the native SVN client, or another client program. I like TortoiseSVN
on Windows and recommend it.

 

I'm being a bit general here because I cannot explain the technical details
of the repository format. There should be no reason why you would need to
enter the repository itself, except maybe in some really unusual
circumstances. Even maintenance is done with SVN commands and scripts.

 

It might help if you posted a bit more about what you are trying to do, or
what you are expecting about what SVN is doing. That would help in deciding
whether something is wrong, and not simply not what you are expecting.

 

Erik

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2402562

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-10-01 17:13:42 CEST

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.