Empty logentry block in 'svn log --xml'

[John Christopher Turner <ct...@thoughtworks.com>]

Something odd is happening to a user of Cruise that we don't
understand... He has an svn server that when the following svn log
command is executed, the xml response back contains an empty logentry
block.

Environment:
  OS Information: Windows Server 2008 6.0
  Subversion: command-line client version 1.6.6.

Command being executed:
  svn --username *** --password *** log --non-interactive --xml -v
--limit 1 svn://hostname/url/path

Response:
  <?xml version="1.0"?>
  <log>
    <logentry revision="3861">
    </logentry>
  </log>


We made the assumption that there would always be content in that
section, but that was clearly invalid. Any ideas on what the cases are
where this could possibly happen?

Thanks,
Chris Turner
Cruise Developer
ThoughtWorks Studios

Re: Empty logentry block in 'svn log --xml'

[Tyler Roscoe <ty...@cryptio.net>]

On Fri, Feb 26, 2010 at 12:56:32PM +0530, John Christopher Turner wrote:
> Command being executed:
>   svn --username *** --password *** log --non-interactive --xml -v
> --limit 1 svn://hostname/url/path
> 
> Response:
>   <?xml version="1.0"?>
>   <log>
>     <logentry revision="3861">
>     </logentry>
>   </log>
> 
> 
> We made the assumption that there would always be content in that
> section, but that was clearly invalid. Any ideas on what the cases are
> where this could possibly happen?

This may be a dumb question but is there a commit message for revision
3861? AFAIK svn has no problem with empty commit messages.

tyler