Philip Martin wrote:
> Julian Foad writes:
>> When bulk-copying from or to a live (writable) repo, there is also the
>> issue of knowing which revision the locks belong to. [...]
>
> Is "the value of HEAD when we read" well defined in all cases? [...]
> For each lock there are two read operations
Julian Foad writes:
> When bulk-copying from or to a live (writable) repo, there is also the
> issue of knowing which revision the locks belong to. In general, a
> lock is applicable only for a particular revision (or revision range),
> as it becomes inapplicable if the file is deleted, at least.
Philip Martin wrote:
> Bulk copying locks is a similar issue to bulk copying revprops. [...]
> We should have a better method.
I fully agree.
> At a minimum we need a new FS API that
> allows the lock's creation date to be specified.
Yes, that's one thing that's
Bulk copying locks is a similar issue to bulk copying revprops. There
is no easy way to bulk copy locks from a repository to a copy of the
repository (even hotcopy has problems: issue 3750).
As with revprops I can write a script using the bindings (see below).
However this script is less useful
4 matches
Mail list logo
