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

Re: can of worms: custom props in our tree?

From: Philip Martin <philip_at_codematters.co.uk>
Date: 2003-11-06 22:47:39 CET

Greg Noel <GregNoel@tigris.org> writes:

> On Wednesday, Nov 5, 2003, at 20:10 US/Pacific, Chia-liang Kao wrote:
>> The question was if it's appropriate for me to have a 'svk:merge'
>> dir_prop to [public] '/trunk'. ... currently the merge info has to
>> be set on the anchor of branching.
> I'm probably asking the wrong question, but why is it necessary to put
> this information in the public repository instead of the local
> repository?

[I don't know anything about svk's design or implementation.]

When there are more than two repositories involved then storing
svn:merge at the merge destination rather than the merge source is the
only way to get the information distributed.

> And if it's in the public repository, what if two (or
> more) people want to use svk to check in at the same point?

They would be using repositories with separate UIDs, and the UID is
stored in svk:merge.

Philip Martin
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Nov 6 22:48:46 2003

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.