[jira] [Commented] (SVN-4454) Allow a commit message to be pulled from HTTP headers for SVNAutoversioning=on

["Paul Hammant (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/SVN-4454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15567414#comment-15567414 ] 

Paul Hammant commented on SVN-4454:
-----------------------------------

Some notes on svnmucc - as recorded by Charles (the proxy) - and completely dcoupled from a subversion checkout, adds new files, like so:

  POST - to start a transaction: Xxx-Yyyy is returned.
  HEAD - to check the new item isn't there (404 response code is expected).
  PUT - to shove the item up 
  MERGE - to commit the transaction

Then changing an existing file, it omits the HEAD for some reason

It'd still be super useful to have a message (a one liner is fine by me) for a single PUT operation with autoversioning/DAV turned on.
Or maybe a <url>?message=xxxx in the same way that <url>?kw=1 is supported for GETs via ModDavSvn.

> Allow a commit message to be pulled from HTTP headers for SVNAutoversioning=on
> ------------------------------------------------------------------------------
>
>                 Key: SVN-4454
>                 URL: https://issues.apache.org/jira/browse/SVN-4454
>             Project: Subversion
>          Issue Type: Improvement
>          Components: mod_dav_svn
>    Affects Versions: 1.8.x
>            Reporter: Paul Hammant
>             Fix For: ---
>
>
> {noformat:nopanel=true}
> There's a stock message that's attached to auto-commits:
>    Autoversioning commit: a non-deltaV client made a change to /xxxxx
> If there were a HTTP header present for the PUT, like "Subversion_Commit_Message", it could be used 
> instead.  The one as listed above, would be the fallback.
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)