[Trimming dev@]
On Thursday 21 December 2006 07:19, Dave_Thomas mailing lists wrote:
> A user's made a series of changes to his working copy, which include
> creating some files (they're unversioned), and deleting others (they're
> missing).
>
> Another user of the same repo needs to make the same changes.
>
> The natural thing would be to copy the working copy from one machine to
> another. But shouldn't it be possible to avoid the bulk of that transfer?
...
> Maybe someone's already made this tool?
Yes, that's called "svn commit".
Just check in to the repository, and the other user can update - it's as easy
as that!
If these are changes that you don't want on your main development line
(unstable, experimental, only proof-of-concept), use a branch.
You can switch the working copy without loosing the changes, so there should
be no problem.
Regards,
Phil
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Dec 21 14:34:51 2006