tty safe. If this patch series
introduced a problem then it is one of the read queries in lib_repos
not returning the latest data when they should. And those invocations
are easy to review.
-- Stefan^2.
> *From:* Stefan Fuhrmann [mailto:stefan.fuhrm...@wandisco.com]
> *Sent:* zondag 11 okto
: Efficient revprop access in lib_repos
[This is the rationale and additional documentation to an upcoming
set of commits.]
When changing a revprop, we provide the following visibility guarantees:
1. A request that ends before the set_revprop started, sees the old value
(duh!).
2. A request that
From: Stefan Fuhrmann
> Sent: 11-10-2015 14:25
> To: Subversion Development
> Subject: Efficient revprop access in lib_repos
>
> [This is the rationale and additional documentation to an upcoming
> set of commits.]
>
> When changing a revprop, we provide the following
tefan Fuhrmann"
Sent: 11-10-2015 14:25
To: "Subversion Development"
Subject: Efficient revprop access in lib_repos
[This is the rationale and additional documentation to an upcoming
set of commits.]
When changing a revprop, we provide the following visibility guarantees:
1.
[This is the rationale and additional documentation to an upcoming
set of commits.]
When changing a revprop, we provide the following visibility guarantees:
1. A request that ends before the set_revprop started, sees the old value
(duh!).
2. A request that starts after the set_revprop completes,
5 matches
Mail list logo
