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

Re: To Greg Stein

From: Greg Stein <gstein_at_gmail.com>
Date: Mon, 18 Aug 2008 06:04:40 -0700

On Mon, Aug 18, 2008 at 5:41 AM, Karl Fogel <kfogel_at_red-bean.com> wrote:
> Branko Čibej <brane_at_xbc.nu> writes:
>> In general I dislike creating branches if the same work can be done on
>> trunk without affecting the rest of the code. And I don't see a
>> problem with including such work-in-progress code in a release.
> side: the bulk of the work is going into new files anyway, so if one
> wanted to review the "state of wc-ng" at any point, one would just look
> at those files. This will remain true until the work starts touching
> libsvn_client, and at that point, I'd much rather have it in trunk so we
> can keep the changes closely coordinated with old libsvn_wc maintenance.)

I think we may have different assumptions here:

* sounds like you're thinking of a new WC library which _client starts to use
* I'm thinking rewrite WC under the covers

Basically, my thinking is: if I can avoid touching _client, then I've
done my work properly.

So your basic statement about "when it touches" is valid, but it is
_wc rather than _client. And per my other note, that is the
no-going-back point when we need to make a decision w.r.t the 1.6

Received on 2008-08-18 15:05:02 CEST

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.