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
Ivan Zhakov wrote:
> As far I remember this thread about two pools paradigm itself
> (result_pool and scratch_pool). It's not about making all functions
> follow two pools paradigm.
Correct.
> Some of API introduced in 1.9 doesn't
> follow this paradigm for some reason.
Yes, I see that.
> Ple
I (Julian Foad) wrote:
> Issue #4598 "No-op changes no longer dumped by 'svnadmin dump' in
> 1.9", http://subversion.tigris.org/issues/show_bug.cgi?id=4598
>
> Added to the release notes in http://svn.apache.org/r1704822 :
> file:///home/julianfoad/src/svn-site/publish/docs/release-notes/1.9.html#n
(New thread, taken from an observation in the "No-op changes no longer
dumped..." thread. In that thread, I hadn't spotted that it is only
the props comparison.)
Starting from 1.9.0, the FS API content comparison methods
svn_fs_contents_changed()
svn_fs_contents_different()
svn_fs_pro
(My second-last paragraph was redundant, saying the same as the bit before it.)
- Julian
I (Julian Foad) wrote:
> * This test looks includes a case where text and a property are set
> to two versions of 'evil' text thay yield the same MD5 sum. I
> initially thought this case would ensure test
5 matches
Mail list logo