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

Julian Foad wrote:
> Michael Sinz wrote:
>
>> Julian Foad wrote:
>>
>>> 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)
>
>
> No. Standard shells expand "{...}" in full without looking at what
> files exist (in contrast to "[...]").

Oops - that is what I get for reading too quickly...

Still, the question is how do I know if I gave a bad path to svn info
when run from a script?

-- 
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