RE: fsfs storage

        From: NS Klanten
        Sent: Monday, 11 May 2015 6:20 AM
        Subject: fsfs storage
        
        
        Hello all,

        Where are the "initial" or base text files (source codes) are stored in fsfs storage ?

        I commit a new source code to my svn server, however after searching all the related svn folders in my server, I can not find the plain text file. I assume that source code is just stored as plain text in fsfs storage and it isn't hashed, is my assumption correct?

        Thanks in advance for your help,
        Jennifer Brooks.

Hi Jennifer,
 
The files are stored in original format in your working copy under ./.svn/pristine/*, but with hashed names.
 
On the server, they're stored under ./db/revs as a series of deltas. If you look at ./db/revs/0 with a text editor, for example, you'll see it starts with the word "PLAIN". Every other file from there on starts with the word "DELTA". For the sake of efficient storage, there is no plain storage of the original files. You'll find this with many version control systems.
 
If you're only storing text files, there's half a chance of understanding what's stored in the delta files. I wouldn't even consider editing them, though.
 
There is probably a setting somewhere to allow a "shadow" version to be set up somewhere - if not, it would be a nice idea. I know in SourceSafe, I was able to set up "shadow" folders on a server so that changes were automatically updated. I suspect that SubVersion would require a server-side post-commit hook to be written to do the same job. Does anybody have one they could share?

Regards,

Geoff

-- 
Apologies for the auto-generated legal boilerplate added by our IT department:
- The contents of this email, and any attachments, are strictly private
and confidential.
- It may contain legally privileged or sensitive information and is intended
solely for the individual or entity to which it is addressed.
- Only the intended recipient may review, reproduce, retransmit, disclose,
disseminate or otherwise use or take action in reliance upon the information
contained in this email and any attachments, with the permission of
Australian Arrow Pty. Ltd.
- If you have received this communication in error, please reply to the sender
immediately and promptly delete the email and attachments, together with
any copies, from all computers.
- It is your responsibility to scan this communication and any attached files
for computer viruses and other defects and we recommend that it be
subjected to your virus checking procedures prior to use.
- Australian Arrow Pty. Ltd. does not accept liability for any loss or damage
of any nature, howsoever caused, which may result
directly or indirectly from this communication or any attached files.