RE: svk behaviour

> > What I mean is, if svk uses an svn repository but adds its own
> > meta-data which it manipulates when you use the provided
> svk commands
> > (commit, add, rm etc.) will it still work as intended if you use svn
> > commands to commit, add etc. instead?
>
> Yes. For example, clkao maintains a private repository of subversion
> itself. He commits fixes to perl-bindings to this private repository,
> then occasionally "pushes" these changesets from his private
> repository
> to the public svn repository. We end up getting one extra 'svk:'
> property attached to our public /trunk/ directory. It's completely
> ignored by vanilla svn tools, and only used by svk.

Right. I understand that as far as svn is concerned it's just an svn repository with some meta-data in. But what happens if you work locally for a while just using svn commands and then try to resync your local repository with the mirror using svk?

Does it matter to svk that you haven't been using svk commands to commit, delete etc, or is it designed in such a way that it 'just works'?

For example, I imagine if I merge my local copy with the master it might combine all of my off-line commits into one, losing an large part of my history. A worse case would be if svk got confused because it found that the local repository had changed while it 'wasn't looking' and didn't let you merge at all.

I don't think I'm being paranoid: just iggerant.

Thanks,
Glenn.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Feb 19 07:22:16 2004