Daniel Shahaf wrote on Mon, 16 Apr 2012 14:48:45 +0300:
> Kuno Meyer wrote on Mon, Apr 16, 2012 at 10:31:33 +:
> > Is it by design that 'svn cleanup' ignores externals and that there is
> no way to
> > include them?
> >
>
> You should be able t
Is it by design that 'svn cleanup' ignores externals and that there is no way to
include them?
I found it a bit inconsistent that 'working copy' has different meanings for
'svn update' and 'svn cleanup'.
Kuno
$>svn help update
update (up): Bring changes from the repository into th
Another unconventional way of accomplishing this would be to use Bazaar's
clean-tree command. With the bzr-svn plugin installed, you should be able to
directly operate on SVN working trees:
bzr clean-tree --ignored --unknown --detritus --force
Mark Phippard gmail.com> writes:
> > With SVN 1.7, is there a way to create a new working copy by cloning a
> > subtree of an existing working copy?
> >
>
> See:
> http://svn.apache.org/repos/asf/subversion/trunk/tools/client-side/detach.py
Thanks. My tests show that the prominently placed co
Stefan Podskubka hcs.at> writes:
> On 20.12.2011 15:44, Kuno Meyer wrote:
> > With SVN 1.7, is there a way to create a new working copy by cloning a
> > subtree of an existing working copy?
> >
> One thing that comes to mind is cloning the existing working copy an
With SVN 1.7, is there a way to create a new working copy by cloning a subtree
of an existing working copy?
For example:
- Already checked out:
wc1/
wc1/.svn
wc1/src
wc1/data
wc1/data/bin1
- Desired: a new working copy of just the "data/" subtree:
wc2/
wc2/.svn
wc2/bin1
A
