On Thu, Apr 19, 2012 at 2:17 PM, Julian Foad <julianfoad_at_btopenworld.com> wrote:
> 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.
>
+1 to any of those improvements :-). Ideally, I'd like to see
something that not only helps getting mergeinfo, but also other props
to make it easier/faster to enforce autoprops (or repository-dictated
props etc ...). In addition something specifically tuned to getting
the mergeinfo answers directly might of course be even better for this
concrete usecase.
--
Johan
Received on 2012-04-19 15:46:31 CEST