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

Re: Should we maintain the backward comaptiblity with Subversion Operational Logging?

From: C. Michael Pilato <cmpilato_at_collab.net>
Date: 2007-06-26 14:02:06 CEST

Malcolm Rowe wrote:
> On Tue, Jun 26, 2007 at 04:07:13PM +0530, Kamesh Jayachandran wrote:
>> The recent enhancements to Subversion operational logging to trunk won't be
>> backward compatible.
> I don't really know how much of a problem that is - did we ever promise
> that it would be?
>> 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.
> I couldn't parse that, sorry.

I think Kamesh is saying that there are two routes we might takes with this
logging stuff:

   - add new items at the ends of their respective lines, as a sort of
     backwards-compat attempt

   - have revisions always be at the ends of lines, for more consistent

and then he points out that the two routes are already in conflict because
in 1.5.0-dev we've added new fields that aren't revisions.

C. Michael Pilato <cmpilato@collab.net>
CollabNet   <>   www.collab.net   <>   Distributed Development On Demand

Received on Tue Jun 26 14:01:57 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.