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

Re: [merge-tracking]Why we need PATH_TXN_MERGEINFO in merge-tracking?

From: Alan Barrett <apb_at_cequrux.com>
Date: 2006-09-14 21:13:06 CEST

On Thu, 14 Sep 2006, Daniel Berlin wrote:
> >So I believe the versioned property like 'svn:mergeinfo' is not supposed
> >to be modified any other process than the one which creates them and
> >hence no cache coherency issue.
> >
> This is an incorrect statement of what the API allows.
> Whether we like this or not, it is the way it is. It does allow the
> property to be modified by other processes.

I thought that propertes with names that begin with "svn:" were special,
and that hitherto-undefined properties of that form were reserved
for internal use, and that any use at all of such such undefined but
reserved properties is, well, undefined. If that is indeed the case,
then it seems to me that you can say that the existing API provides no
way at all do do anything with the new svn:mergeinfo property. Then you
can define a new API for it without violating any backward compatibility
guarantees. The new API for svn:mergeinfo could be "just like the API
for other properties, except <X> is not guaranteed".

OK, it's a weak argument, but I think you could make it if you really
wanted to.

--apb (Alan Barrett)

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Sep 14 21:15:18 2006

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.