> On Mar 2, 2019, at 8:21 AM, Daniel Shahaf <d.s_at_daniel.shahaf.name> wrote:
>
> wuzhouhui wrote on Fri, Mar 01, 2019 at 17:46:55 +0800:
>>> -----Original Messages-----
>>> From: "Branko Čibej" <brane_at_apache.org>
>>> Sent Time: 2019-03-01 17:16:40 (Friday)
>>> To: users_at_subversion.apache.org
>>> Cc:
>>> Subject: Re: How to open specified inside .svn
>>>
>>> There are no such generic functions. The svn_wc API isn't really meant
>>> to be public, so you'll have to write your own access functions. Look at
>>> how the svn_client implementations do it, or for example
>>> svn_wc__get_pristine_contents_by_checksum in svn_wc_private.h.
>>
>> Actually, I'm hacking Subversion client command line tool, so it
>> doesn't matter whether the API is public or private.
>
> The difference isn't just visibility. We don't promise compatibility
> for private APIs, not even across patch releases in the same minor line
> (1.A.x and 1.A.y).
Thanks for your reminding. I have implement client side pre-commit hook.
The implementation maybe ugly, but it works at least.
In case of someone have interests, you can find my customized Subversion
in https://github.com/wuzhouhui/subversion. Please forgive me about using
Git to version control Subversion :-)
Received on 2019-03-02 05:29:47 CET