Re: Feature request: allow for relative working copy paths in svn:externals definition

On Fri, 02 Mar 2012 14:54:38 +0000, Humm, Markus wrote:
...
> In my eyes nothing beats the simplicity and understandability of
> svn:externals with one single level deep relative paths
> to a directory above.

Exactly as long as you don't try to do

   svn checkout http://your/soft/ware/trunk dir-a
   svn checkout http://your/soft/ware/trunk dir-b

in one and the same directory (namely $HOME, where I do this all the
time).

> Software should adopt as good as possible to the
> existing workflow/structures. There should be no
> need to completely rearrange projects just to get what one wants only

'completely rearrange' is a bit harsh for putting the CommonFiles
external within instead of besides the tree checked out. Besides,
the very idea of letting a checkout/clone create files outside
of the target directory I specified is foreign to all other version
control systems I used so far.

Andreas

-- 
"Totally trivial. Famous last words."
From: Linus Torvalds <torvalds@*.org>
Date: Fri, 22 Jan 2010 07:29:21 -0800