Automerging (autosynch) of certain branches

I have searched for any mention of this, but I haven't found it, yet.

In our current system, we have a series of projects with release documents
which are both locally and globally numbered:

/svn/prj001/REVA/001-prj001_REVA_rel001
/svn/prj001/REVA/002-prj001_REVA_rel002
/svn/prj001/REVA/004-prj001_REVA_rel003
/svn/prj001/REVB/006-prj001_REVB_rel004
/svn/prj001/REVB/008-prj001_REVB_rel005

/svn/prj002/REVA/003-prj002_REVA_rel001
/svn/prj002/REVB/007-prj002_REVB_rel002

/svn/prj003/REVA/005-prj003_REVA_rel001

The GLOBAL number is to ensure we do not have duplicates, and in production
they ONLY use the global document number because it is universally unique.
Which means that we have a seperate folder for them (production can look up
document ###):

/svn/Prod-docs/001-prj001_REVA_rel001
/svn/Prod-docs/002-prj001_REVA_rel002
/svn/Prod-docs/003-prj002_REVA_rel001
/svn/Prod-docs/004-prj001_REVA_rel003
/svn/Prod-docs/005-prj003_REVA_rel001
/svn/Prod-docs/006-prj001_REVB_rel004
/svn/Prod-docs/007-prj002_REVB_rel002
/svn/Prod-docs/008-prj001_REVB_rel005

So I have two questions.

1) Is there a better way to organize between engineering releases and
production (which retains the simple universal uniqueness)?

2) If not, is there a way to "autosynchronize" the project folder with the
product folder? Because inevitably something needs to be changed one way or
another.

A complicating factor is that the files are often modified and viewed via
WebDAV access.

Any pointers on this tricky issue would be GREATLY appreciated.

Best Regards,

Al

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Apr 20 15:15:36 2006