Oh, I completely agree -- in the vast majority of cases you definitely want to avoid doing it. I'm just explaining why it doesn't throw errors at you.
Cheers - (This list is reply-above isn't it?) On Mon, Jul 11, 2011 at 7:00 PM, Nico Kadel-Garcia <nka...@gmail.com> wrote: > On Mon, Jul 11, 2011 at 9:20 PM, Geoff Hoffman > <ghoff...@cardinalpath.com> wrote: > > This is a feature, yes. Subversion does allow your working copy to point > to > >> 1 svn path. > > Sounds a lot like when you use svn:externals. This may be the more > > "standard" way of achieving what you're talking about. > > If you change code in [yourstuff] and [stuff pointing back to external's > > home] then when you commit (in NetBeans anyway) it will show you a > warning > > about committing to multiple branches. > > You can also svn update a specific file/dir to a specific (older, > non-HEAD) > > revision, though I've rarely if ever done this. > > > > HTH- > > I've not seen it documented anywhere. Frankly, I think it's very > dangerous due to potential conflicts with accidentally left behind > material, especially if "svn:ignore" is used. >
