Andy Levy <andy.levy <at> gmail.com> writes:
>
> On 5/22/07, MikeW <mw_phil <at> yahoo.co.uk> wrote:
> > I have a version of a source tree in SVN.
> >
> > I have been supplied with a patched version of the tree, with
> > some files and directories added, some deleted, some modified.
> >
> > I would basically like the new version of the tree to become the
> > next revision in SVN, with files & directories added, updated,
> > deleted from the repository as appropriate.
> >
> > What would be the 'best practice' way of achieving this, please ?
> > Single commit if possible.
>
> Treat it like a Vendor Branch and load it in using svn_load_dirs.pl
> See
http://svnbook.red-bean.com/en/1.2/svn.advanced.vendorbr.html#svn.advanced.vendorbr.svn_load_dirs
>
Good link to reference, Andy - thanks for that.
A colleague suggested the simple method mentioned in the first part
of that section - to remove all source files from a working copy,
copy the new tree over the 'skeleton' working copy, then use
'svn status' plus grep etc. to perform 'svn rm' etc.
This tool needs better indexing to ensure that it is spotted by those
needing it without having read every chapter !
Thanks again.
MikeW
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue May 22 18:59:51 2007