Re: "svn info" good return code on bad URL

Julian Foad wrote:
> John Belmonte wrote:
>> Julian Foad wrote:
[...]
>> We (inconsistently) treat errors like "not under
>> version control" and "file does not exist" as non-fatal so you can use
>> wildcards. When thinking about this, it only seems to make sense for
>> working copy targets, though. So we could get rid of this for URLs if we
>> wanted to.
>
> Roughly; but "so you can use wildcards [that match more than just the
> intended files]" is only one example of a sloppy usage that is made
> "easier" by the decision. Similar cases do apply to URLs, e.g. "svn
> info $REPOS/branches/1.{0,1,2}.{0,1}" where you don't care if some of
> those combinations don't exist. So no, we shouldn't get rid of that
> behaviour just for URLs.

Now I am confused... I think.

The command above is (in Unix shells) a glob expansion of file names that
only expand to those names that actually exist (the shell checks/looks for
the files)

So, while there would be no error/warning for the combinations that don't
exist, that is because they were never actually passed to the svn info
command. This does not change the fact that if you actually use a file
name that does not exist that a warning (and 1 return code) should be sent,
does it?

-- 
Michael Sinz                     Technology and Engineering Director/Consultant
"Starting Startups"                                mailto:michael.sinz@sinz.org
My place on the web                            http://www.sinz.org/Michael.Sinz
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org