[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: Kamesh Jayachandran <kamesh_at_collab.net>
Date: 2007-06-26 14:18:19 CEST

>>> 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
> parsing
> 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.
Thanks Mike for clarifying, that is what I meant.

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 14:17:12 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.