Chia-liang Kao <clkao@clkao.org> writes:
> > I actually disagree that this would require lots of new code. Also,
> > it does not require updating the uncommitted txn with merges -- that's
> > a further enhancement, not a necessity for the basic feature.
>
> That means any other non-conflicting commit actually got committed would
> render the txn unapplicable, which you will naturely do a merge and
> regenerate the txn. Since you have to do that, I think software should
> probably do it for you.
Sorry, I'm not sure I understand.
If commits come in later, but are non-conflicting with the dangling
txn, then the dangling txn can still be committed at any time. Why
would it be rendered in applicable?
> Actually what svk patch does, with a base root and serialised editor
> calls, is exactly the same as using txn, running delta between its
> base root and txn root. It's just already existing today, and hooked
> with merge code already.
That's exactly what I assume we would do.
-Karl
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Aug 23 03:47:30 2005