Re: Multiple independent repositories

On Mon, Jan 31, 2005 at 04:00:06PM +0000, abcd wrote:
> --- Petr Smr??ka <smrcka@1sig.cz> wrote:
> > There will be a trunk of the project accessible to
> > your client
>
> That's precisely what I don't want to happen. The
> client does not (and should not and will never) have
> the visibility of my machines. Is your procedure
> applicable even in the case of a completely
> independent repository i.e., one residing on a remote
> machine?

In that case, I think you're stuck with the following model:

- In your repo, on the trunk, hack hack hack.

- Create a release for you client by copying to tag. (Or merge into
  client branch, or whatever is appropriate.)

- Export the tag.

- Import the export into client repo.

Of course, by doing this, not much is gained by them having their own
repo; you might as well give a tarball. Hmmm, I suppose them having a
repo might make it easier to preview changes, revert, etc.

Ahhh, the other approach might be SVK, which does support merging
between repositories. But all I know about SVK I read on the web:
http://svk.elixus.org/

Steve

-- 
"Outlook not so good." That magic 8-ball knows everything! I'll ask
about Exchange Server next.
                           -- (Stolen from the net)
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org