[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

rfc for proposal on solving issue #443

From: Madan US <madan_at_collab.net>
Date: 2005-05-05 12:57:46 CEST

  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.

<?xml version="1.0" encoding="utf-8"?>
<D:merge-response xmlns:D="DAV:">
<D:post-commit-status>POST-COMMIT temp message</D:post-commit-status>
   like that!!!!
<D:status>HTTP/1.1 200 OK</D:status>
<D:status>HTTP/1.1 200 OK</D:status>

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

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.