How about XML? It's just 'binish' enough to keep newbies from mucking it,
but is still parsable.
Also, I liked the suggestion of multiple methods -- i.e. if the local data
is not present, the server data is used.
I'm presently using a system from Synchronicity (EDAcentric) that uses
'turd' directories, but is not at all upset if the data is removed -- it
just recreates it from the server data.
> -----Original Message-----
> From: Jonathan S. Shapiro [SMTP:shap@eros-os.org]
> Sent: Friday, August 25, 2000 7:19 AM
> To: dev@subversion.tigris.org
> Subject: Re: Bundles Re: SVN, .SVN, and other meta-data directorys
>
> If people are serious about this, then perhaps the metadata should be in
> binary form? It's more parseable, and only serious experts will screw with
> it in binary form.
>
> ----- Original Message -----
> From: "Karl Fogel" <kfogel@galois.collab.net>
> To: <dev@subversion.tigris.org>
> Sent: Wednesday, August 23, 2000 9:24 PM
> Subject: Re: Bundles Re: SVN, .SVN, and other meta-data directorys
>
>
> > Branko =?iso-8859-2?Q?=C8ibej?= <branko.cibej@hermes.si> writes:
> > > In my (not so humble) opinion, metadata should _only_ be manipulated
> > > via the Subversion client library.
> >
> > The same is true for CVS, but people do it anyway.
> >
> > Subversion will try to give them fewer reasons to.
> >
Received on Sat Oct 21 14:36:07 2006