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

Re: Request: make the user agent string a define

From: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2005-01-09 00:42:58 CET

On Jan 8, 2005, at 4:02 PM, SteveKing wrote:

> Can we just say that many people would like to know (for whatever
> reasons they have, wheter you agree with them or not) with which
> client users connect to the repository and leave it at that?

The truth is, that's just not the way the Subversion project works.
Perhaps it's a philosophical difference between the Subversion and TSVN

My impression is that TSVN has a pragmatic style of development: "if
lots of users ask for it, then it must be something useful, and
therefore it must be something Good and worth doing."

But in the Subversion project we don't believe that. If we hear many
requests for something, we still want to debate the merits of the idea,
offer counter-solutions, and generally consider the impact of such a
feature on the software overall. (For example: we won't implement the
$Log$ keyword, even though people ask about it all the time.)

So your request above doesn't make a lot of sense to us: in our minds,
popularity alone isn't a strong argument for a new feature. We refuse
to say, "well, people have their reasons" and then forget about it.
That's why you see Max and Erik trying to understand *why* users are
asking for the feature.

I really hate the fact that we so often end up getting into stubborn
arguments with you, Steve. We certainly have no ill will towards you,
no matter how it may appear. (I think TSVN is fantastic, and I love
the work you do!) I'd love to see more and more collaboration between
Subversion and TSVN. Don't let these debates frustrate you. :-)

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Jan 9 00:45:07 2005

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.