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

Re: [PROPOSAL] Drop XML from .svn/entries

From: Garrett Rooney <rooneg_at_electricjellyfish.net>
Date: 2006-04-17 01:53:39 CEST

On 4/6/06, Peter N. Lundblad <peter@famlundblad.se> wrote:

> So, I propose to replace our current XML entries files with some
> variant of this new format. Below is three lines from an entries file
> to show how it might look:
>
> |dir|2|file:///home/pl/svntest/gcc/repo|file:///home/pl/svntest/gcc/repo||||2006-04-06T20:31:40.024395Z|2|pl|t||svn:special svn:externals svn:needs-lock||||||||||||b4f160ba-c4e8-11da-bcd8-65faf9067726|
> config-ml.in|file|||||2006-04-05T21:35:10.000000Z|e09724e0a7725cc08129db9293a35df9|2006-04-05T21:20:33.744115Z|1|pl|
> libgomp|dir|
> ...
>
> Each entry is on a separated line and each field is terminated by a |
> character. Empty fields may be omitted provided all following fields
> are also empty. Absent fields are represented by empty fields (except
> for the entry name, where an empty field means the thisdir entry).
> Boolean values are represent by "t" (for true" or an empty field for
> false. IN the future, we can add new fields at the end of each
> record. There will be an escaping mechanism for control characters
> (think newlines in lock comments) and the | separator.

Something that came up in conversation with jerenkrantz today...

Why not switch from pipe delimited to newline delimited fields? One
newline would delimit fields in an entry, a line with just a newline
on it would indicate a new entry. I suppose we might need some way to
indicate an empty field, but that should be easy enough, or heck, you
could even go based on the known number of fields in an entry, using
the blank line between entries as a sanity check. It would result in
far more easily readable entries files, and the size would be
identical...

-garrett

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Apr 17 01:54:09 2006

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.