> -----Original Message----- > From: Daniel Shahaf [mailto:danie...@elego.de] > Sent: 16 April 2012 12:49 > To: Kuno Meyer > Cc: users@subversion.apache.org > Subject: Re: 'svn cleanup' ignores externals > > Kuno Meyer wrote on Mon, Apr 16, 2012 at 10:31:33 +0000: > > Is it by design that 'svn cleanup' ignores externals and > > that there is no way to include them? > > > > You should be able to include them by naming them explicitly: > > % svn cleanup path/to/external/dir > > > I found it a bit inconsistent that 'working copy' has > > different meanings for 'svn update' and 'svn cleanup'. > > > > I think we can fix that in 1.8. We have --include-externals and > --ignore-externals flags; we just need to decide whether to include > externals by default or not. > > Daniel
I would vote for `--include-externals` as the default. I agree with the OP that this is a confusing issue. Alterntively the `run cleanup` message should specify to use `--include-externals` (if required) otherwise it looks like the suggested fix doesn't work and leaves you in a cycle. Just by tuppence. ~ mark c > > Kuno > > > > ------------ > > > > $>svn help update > > update (up): Bring changes from the repository into the > working copy. > > > > $>svn help cleanup > > cleanup: Recursively clean up the working copy, removing > locks, resuming > > > > ------------ > > > > $> svn up <wc_root> > > > > Fetching external item into '<some_other_path>': > > svn: warning: W155037: Previous operation has not finished; > run 'cleanup' if it > > was interrupted > > > > At revision 62460. > > svn: E205011: Failure occurred processing one or more > externals definitions > > > > $> svn cleanup <wc_root> > > > > $> svn up <wc_root> > > > > Fetching external item into '<some_other_path>': > > svn: warning: W155037: Previous operation has not finished; > run 'cleanup' if it > > was interrupted > > > > At revision 62460. > > svn: E205011: Failure occurred processing one or more > externals definitions > > > > >
