I know you're not supposed to, BUT...

    I am using Subversion for cross-repository merging. The two repos
have identical file/directory structures, so changes only occur within
files. When I do need to create a new file or directory, I simply do so
in both repositories independently, and then merge. The merge procedure
goes a little
something like this:

    1) Change is made in working copy of repository Alpha, and
committed.
    2) Working copy of repository Beta is merged with appropriate
revisions of repository Alpha
    3) Working copy of repository Beta is then committed to Beta with
the changes from the revisions in Alpha included.

    Am I headed for disaster? Does anyone know or foresee any problems
this will cause in my repositories?

Any thoughts on the subject are appreciated,
Mike.

--
Michael Stabler     703.883.7461
Software Engineer   mstabler@mitre.org
CSSI, Inc.
MITRE-CAASD
M/S N370
7515 Colshire Drive
McLean, VA 22102-7508
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org