Re: About them "broken pipes"

On Nov 3, 2007, at 3:27 PM, Julian Foad wrote:

> I propose this rule:
>
> When svn is performing a read-only subcommand[1]:
> on attempting to write to stdout and finding it is a broken pipe:
> svn should clean up and then terminate without printing an error
> message.

I'm tempted to add to this list "and stdout is not a plain file," but
this may not be a portable concept. Probably the "broken pipe"
qualifier is enough, here, as plain files can't have that outcome.

-==-
Jack Repenning
Chief Technology Officer
CollabNet, Inc.
8000 Marina Boulevard, Suite 600
Brisbane, California 94005
office: +1 650.228.2562
mobile: +1 408.835.8090
raindance: +1 877.326.2337, x844.7461
aim: jackrepenning
skype: jrepenning

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Nov 5 21:33:06 2007