Re: [PATCH] issue #3620: svn add ^/ triggers assertion failure

On Fri, Apr 23, 2010 at 4:24 PM, Stefan Sperling <stsp_at_elego.de> wrote:

> ...
>
> We should also consider changing the way "^/" is interpreted.
> Maybe only commands that expect URLs as arguments should expand "^/"
> to a URL? That way the above error would become:
>
> $ svn add ^/
> svn: warning: '/path/to/working/copy/^' not found
>

I think it's best to consistently expand "^/". In my mind the above should
be interpreted as:
$ svn add http://svn.example.com/repos/

which would then generate whatever warning it should.

The shell doesn't selectively expand wildcards and such depending on the
Subversion command; selective expanding our own syntactic shortcuts would
just lead to more confusion.

-Hyrum
Received on 2010-04-23 23:56:35 CEST