abcd wrote:
>Hi all,
>
>I'm developing this large system for a client. I've
>got my own private (i.e., not accessible by the
>client) svn repository. My client, on the other hand,
>wants a repository of her own. This should not be an
>exact copy of mine, as she only wants the most
>important releases, not just every minor bug fix
>(which BTW sounds pretty reasonable to me). Problem
>is: How can I achieve this? Ideally, I would like to
>be able to do something along the lines of:
>
>make minor changes to WC (e.g., fix a bug)
>commit to my repo only
>do major work
>commit to my repo
>magically switch to client's repo
>commit to client's repo
>switch back to mine
>
>Conceptually, a commit to the client's repo should
>more or less correspond to a tag (i.e., a "memorable"
>release). Anyone knows how I can do this (easily if
>possible since I'll have to do it frequently)? I read
>the manual but I wasn't able to find anything
>appropriate.
>
>Thanks a lot,
>Andy
>
>
>
That's exact idea of concept of branches and merges. So if I have to
manage this I would do it this way:
There will be a trunk of the project accessible to your client and you
will work on a branch of trunk which
can not be accessed by your client. Anytime You would like your client
to see your minor changes made
to a project you will merge them to trunk with appropriate log message
which your client can understand
menawhile logs in your branch will be suitable to your needs.
Second way how to handle this leads through exporting your project
directly to your client. by the first one
is more comfortable and consistent. I suppose yout client doesn't commit
to project but even if he does, he can,
only merging may become less comfortable because of conflicts.
Hope it can help
--
Smrk
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Jan 31 13:21:00 2005