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

Re: [RFC] Make svnserve require --inetd to use stdin/stdout

From: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2004-01-03 17:30:19 CET

On Sat, 2004-01-03 at 10:16, Tobias Ringström wrote:
> I'd like to make svserve require an -i/--inetd option in order to use
> stdin/stdout. The default mode would simply be to print an error and a
> nice usage message. I believe that most people who run svnserve really
> intend to use the -d or -t options, and that it's better to be helpful
> to them than to make the (as I believe) less common inetd mode the default.

I dunno what Greg Hudson thinks, but is this really a problem? Have you
seen all sorts of people run 'svnserve', see spew on stdout, and then
get confused, wondering if it's running or not? I certainly haven't.

I posit that it's basically impossible to get either svnserve or apache
working without reading *some* kind of documentation, and at the moment,
the *very* first thing that both the Book and man-pages say about
svnserve is that it communicates with stdin/stdout.

I have close to zero sympathy for people who try to run svnserve without
reading any documentation at all. So to me, this change feels like
either (a) fixing a problem that doesn't really exist, or (b) being
sympathetic to users that don't deserve it.

But that's just me. :-)

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Jan 3 17:30:57 2004

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.