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

Re: WC -> WC copy/move operations and repository access

From: Mark Phippard <markphip_at_gmail.com>
Date: 2007-09-19 18:46:16 CEST

On 9/19/07, C. Michael Pilato <cmpilato@collab.net> wrote:
> Mark Phippard wrote:
> > I hate the idea of svn cp contacting the repository. I think we all
> > do. Where I think I differ from everyone else is that I am not
> > convinced that creating the mergeinfo in a WC to WC copy is vital. At
> > least in terms of a release stopper.
> Mark, I know I suggested this on the phone call we had about this topic, but
> I can't recall why it wasn't feasible:
> Can our mergeinfo querying logic not just grow smart enough to realize
> that, duh, a copy in an item's history necessarily means that the
> pre-copy revisions are already part of the item's history -- and by
> extension, part of its mergeinfo -- too?
> The rebuttal to this was, I think, that we won't know the difference between
> "mergeinfo for the copy was never recorded" and "mergeinfo was explicitly
> removed". But that doesn't make sense to me, and further, seems like we'll
> be starting off the bat with bogus assumptions when using pre-1.5
> repositories. (Surely not every copy made pre-1.5-upgrade carries an
> explicit desire to unrecorded mergeinfo, right?)
> It's likely, though, that I'm misremembering here. Can you set the record
> straight?

Heh, I'd rather Dan do that :)

Correct me if I am wrong, but the road you are going down is the
"defer creating the info" until commit time? The commit can see that
it is committing a copy and create the mergeinfo at that time?

I think (also trying to remember) the main issue is/was that we made
this decision to use SVN properties so that people could manually edit
mergeinfo, and that becomes a problem in this scenario as we do not
know if that has happened or not. I am not sure how the pre-1.5
repositories factor into this.

One issue in terms of deferring the creating of mergeinfo is do we
have the information we need to create the mergeinfo later, at time of
commit? I think the answer is yes.

Could we get around the property editing problem by inserting a
property value that tells us to create the info at commit time? Is
that too ugly?

Mark Phippard
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Sep 19 18:46:29 2007

This is an archived mail posted to the Subversion Dev mailing list.