Madan U Sreenivasan writes:
> Hi,
>
> <quote>
> Also, note that recently some code from the Dawn of Days of the Subversion
> project has been revived. It implements an XML (de)serializer for editor
> drive data, which means it can spit out an XML representation of a set of
> changes, and can take that XML representation and use it to "patch" a
> pristing set of files. The other existing (de)serializer today is the one
> that is commonly known as the "dumpfile" format. These two existing
> implementations need to be taken into account during the analysis and
> design phase.
> </quote>
>
> I do not unerstand what this means completely. Could somebody
> enlighten me pl? Maybe its simply hard for a SoC candidate to
> understand, which means we should simplify the wording.
>
It means that there is some old work to consider when designing a new format.
One is an extended, XML-based, patch format. It will represent subversions
internal way of describing a change (a so called editor drive, see svn_delta.h)
as a set of XML elements.
The other format one might want to look at is the format produced by
svnadmin dump. That's a MIME-like format.
Note that SoC is closed for new applications, so we may not need to clarify
it for that reason for some time:-)
> Also, Pl. note the word 'pristing'. I think this obviously is
Fixed in r19734. Thanks.
//Peter
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon May 22 08:43:28 2006