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

Path order in svn log xml output

From: Yves Bergeron <yves.bergeron_at_shq.gouv.qc.ca>
Date: 2006-04-25 19:47:58 CEST

Hi everybody,
I use Subversion 1.3.1 on a Solaris server.

When I do svn log --verbose, I might obtain something like this:


r10 | shqybn | 2006-04-25 13:16:05 -0400 (Tue, 25 Apr 2006) | 1 line
Changed paths:
A /trunk/plsql (from /trunk/sql:2)
R /trunk/plsql/svnt_fnb_fonction.fnc (from
D /trunk/plsql/svnt_jab_fonction.jav
A /trunk/plsql/svnt_jab_java.jav (from /trunk/sql/svnt_jab_java.jav:9)

A /trunk/plsql/svnt_pkb_package.pkb (from
A /trunk/plsql/svnt_pkb_package.pks (from
A /trunk/plsql/svnt_prb_procedure.prc (from

Revision 10
It means that after the copy of a directory, Subversion reproduced in
the new directory all the file manipulations made in the original
directory since the revision of that directory. In that report, the
order of operations is very significative.
When I do svn log --verbose --xml, I might obtain something like this
for the same repos/revision:
<?xml version="1.0" encoding="utf-8"?>
<msg>Revision 10</msg>
As you see, the order of operations (paths) is not the same and not
very comprehensive. I would like the sequence of paths be the same as
svn log without the --xml flag. It's important for me when I try to
reproduce in a SQL database all the operations made on a repository.
With the XML output as it is now, it's not possible.
That situation might be a bug or an oversight of the way someone might
use the XML output. If necessary, I will forward this message to the
dev list.
Thank you.

« Le présent courriel peut contenir des renseignements confidentiels et ne s'adresse qu'au destinataire dont le nom apparaît ci-dessus. Si ce courriel vous est parvenu par mégarde, veuillez le supprimer et nous en aviser aussitôt. Merci. »
Received on Tue Apr 25 19:50:08 2006

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

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