Hi,
This is regarding issue #443. I'm thinking of a solution and wanted
all possible comments I could get before I get deeper. Pl. let me know
what you think of the below proposed solution.
#443 is about propagating the post-commit hook failure back to the
client. I propose a minor change to the merge-response that is being
sent back from the mod_dav_svn. The client side would be able to parse
this while parsing other stuff like revision et al. then the client
would display a warning that the post-commit hook has failed.
Pl. refer to the merge-response below for a sample xml with the
post-commit error message.
Thanks,
Madan.
----------------------------------------------------------------------
<?xml version="1.0" encoding="utf-8"?>
<D:merge-response xmlns:D="DAV:">
<D:updated-set>
<D:response>
<D:href>/repositories/basic_tests-3/!svn/vcc/default</D:href>
<D:propstat><D:prop>
<D:resourcetype><D:baseline/></D:resourcetype>
<D:post-commit-status>POST-COMMIT temp message</D:post-commit-status>
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
like that!!!!
<D:version-name>40</D:version-name>
<D:creationdate>2005-05-05T10:56:43.520006Z</D:creationdate>
</D:prop>
<D:status>HTTP/1.1 200 OK</D:status>
</D:propstat>
</D:response>
<D:response>
<D:href>/repositories/basic_tests-3/iota</D:href>
<D:propstat><D:prop>
<D:resourcetype/>
<D:checked-in><D:href>/repositories/basic_tests-3/!svn/ver/40/iota</D:href></D:checked-in></D:prop>
<D:status>HTTP/1.1 200 OK</D:status>
</D:propstat>
</D:response>
</D:updated-set>
</D:merge-response>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu May 5 12:58:52 2005