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

Re: more editor v2 (3)

From: Greg Stein <gstein_at_gmail.com>
Date: Fri, 18 Sep 2009 00:48:18 -0400

I'm in an airport on my phone, so this will be short: I suspect you have
nothing to worry about at all.

Please specify the concrete case you're concerned with. Where did that text
delta come from that is being spooled to apply? (and note my earlier email
about the four cases over the wire)


On Sep 17, 2009 5:58 PM, "Augie Fackler" <lists_at_durin42.com> wrote:

On Sep 16, 2009, at 8:43 PM, Greg Stein wrote: >> What makes most sense to
me: >> - REPOS gets the...
If I'm understanding this right, then this makes Ev2 a lot less flexible
than Ev1. I'm using Ev1 in hgsubversion - the ability to just drop some
edits on the floor without needing a base text is *invaluable*. The case I
care about is usually something like this:
M /wiki/blah.wiki
M /trunk/foo/bar.txt

Where I do care about edits to trunk, but /wiki is outside of any tree I
track. With the current editor interface, I can just pass a noop handler to
txdelta_apply() and it's no big deal that I don't have a base text. It
sounds like (and please, correct me if I'm wrong) in Ev2 that this would
incur the overhead of hitting the server for a BASE for blah.wiki,
reconstruct the new blah.wiki, which I'd then drop on the floor anyway. Is
that right?

Not that I'm necessarily saying you have to care - but the existing API
works very well for extremely unusual applications, and it sounds like the
new one isn't nearly as flexible for slightly kooky things.

Received on 2009-09-18 06:48:38 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.