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

Should we maintain the backward comaptiblity with Subversion Operational Logging?

From: Kamesh Jayachandran <kamesh_at_collab.net>
Date: 2007-06-26 12:37:13 CEST

Hi All,

The recent enhancements to Subversion operational logging to trunk won't
be backward compatible.
I am attaching difference in logs of 1.5.0-dev and 1.4.4.

Maintaining the backward compatibility may be possible if we add new
fields at the end.(Depends on how people parse it).

But I have one more improvement in mind that won't allow adding fields
at the end.
The improvement is consistent style of fields like revision should be
the last field, so that parsing would be easier.
i.e In 1.5.0-dev for 'checkout' we added revision number for commit and
we added the 'common-parent-of changed-paths' to commit, adding this new
info at the end would break the above improvement of consistent logging.

1.4.4 1.5.0-dev
commit r8 commit
'/trunk' r8
list-dir /trunk list-dir
'/trunk' r8
blame /trunk/test.c blame
'/trunk/test.c' r8:17
diff-or-merge '/left_path' '/right_path' diff-or-merge '/trunk'
r5:9 Or diff-or-merge '/left_path@84' '/right_path@94'
switch '/source_path' '/destination_path' switch '/left_path@84'
checkout-or-export '/trunk' checkout-or-export
'/trunk' r8
update '/trunk' update
'/trunk' r8
remote-status '/trunk' remote-status
'/trunk' r8
log-all '/trunk' log
'/trunk,/branches/abc' r8:18"
log-partial '/trunk' log
'/trunk,/branches/abc' r8:18"

In summary I would like to go-ahead with the format of
'command path(s) rREV".
This needs a change to 'revprop-change' log and 'replay'
revprop-change r8, 'svn:log' -> revprop-change 'svn:log' r8
replay 8 '/trunk' -> replay '/trunk' r8

With regards
Kamesh Jayachandran

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Jun 26 12:36:29 2007

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.