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

Re: Thoughts and open questions on patch/dump unification

From: Max Bowsher <maxb_at_ukf.net>
Date: 2004-09-17 02:51:42 CEST

Eric S. Raymond wrote:
> I feel a need, at this point, to observe that I am *not* the person who
> brought up the merits or demerits of Perl as an svk issue.

You did say:
>>> I think svk is a clever idea, but I would prefer to see support for
>>> decentralized development integrated into the subversion core and done
>>> in a cleaner way. At the very least I'd be happier if the
>>> svk-equivalent
>>> stuff were in Python, which I think has better long-term
>>> maintainability.

Dave Rolsky replied:
>> So basically you have no meaningful criticism here, you just want to
>> start
>> a language war. Good idea. Then we can fight about emacs vs. vim
>> afterwards!
>> Seriously, _you_ might be happier if it were in Python, but other people
>> wouldn't be. Who cares? Unless you plan to write an SVK-alike in Python
>> what's the point of bringing this up?

Eric S. Raymond wrote:
> So to those
> of you who accused me of wanting to start a language war, kindly get
> stuffed.

Dave's rebuke was a little confrontational. But it does contain a valid
statement - unless you are planning to rewrite SVK in Python, what was the
point of mentioning Python at all here?

Discussing relative maintainability is somewhat irrelevant when one
implementation exists and the other does not.


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Sep 17 02:57:17 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.