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

Re: Merge policies

From: Julian Foad <julianfoad_at_btopenworld.com>
Date: Thu, 19 Apr 2012 13:17:13 +0100 (BST)

Johan Corveleyn wrote:
> I haven't read your mail in detail yet, but [...] propgetting
> ('svnlook propget') every changed file during pre-commit can be very
> expensive.
[...]
> The problem is mainly that 'svnlook propget' doesn't support recursive
> propgetting, nor getting all props from the entire transation, or ...
> only the props for a single path. Which means you have to invoke it
> separately for every item that needs to be inspected. Maybe that can
> be improved somehow?

Of course that can be improved.  Let's attack the source of the problem here.  If we want to use 'svnlook' to discover what mergeinfo is changing in the proposed commit, then we can write a function/subcommand that answers that question directly.  Or a subset of it (e.g. recursive propget) or a superset of it (e.g. get higher level merge graph-change info directly), whatever is effective.

- Julian

>
> Anyway, these are just some slightly OT random thoughts.
Received on 2012-04-19 14:17:49 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.