[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: About them "broken pipes"

From: Julian Foad <julianfoad_at_btopenworld.com>
Date: 2007-11-06 02:55:01 CET

Jack Repenning wrote:
> 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.

Filed as issue #3014 <http://subversion.tigris.org/issues/show_bug.cgi?id=3014>.

- Julian

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Nov 6 02:55:18 2007

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.