-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I was just thinking about that, and I like it too. Also, there should be some
mechanism (the default, hopefully) to automatically decode based on the
Content-Transfer-Encoding (base64).
When someone sets a binary property, by default, the client should
automatically insert the headers and encode in Base64. Propset, propget, and
propedit should have options to allow manipulation of the raw encoded headers
and body as well.
$ svn pset bin:icon -F icon.png foofile
$ svn pedit --raw bin:icon foofile
Content-Type: image/png /* change to this */
Content-Transfer-Encoding: base64
AAAAdGhpcyBpcyBhIHRlc3QK...
$ svn ci ... other stuff
$ svn pget bin:icon foofile > icon.png
On second thought, why not do this for all properties internally, but by
default the mime-type is "text/plain;charset=UTF-8" for all non-"bin:*"? No
need for a new fs schema, but it easily allows meta-metadata. Or is this all
too much to solve a presumably rare edge case?
On Wednesday 04 December 2002 16:06, Glenn A. Thompson wrote:
> I like the previously mentioned:
>
> bin:DoHickey
> Content-Type: application/octet-stream
> Content-Transfer-Encoding: base64
> AAAAdGhpcyBpcyBhIHRlc3QK
>
> People see/use this kind of stuff all the time in e-mail.
>
> It also allows non-SVN savvy programs or shell scripting languages to
> create property files which can be fed to svn via -F arguments.
- --
Peter Davis
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
iD8DBQE97p20hDAgUT1yirARAmLhAKCatNvIRgNSH+0yEKf3keoLrvQUjACeJBgm
TvJncMTy3TSdxRxiW/RinZA=
=eBYF
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Dec 5 01:29:26 2002