> "B. W. Fitzpatrick" <firstname.lastname@example.org> writes:
> > Ben, this is mostly directed to you.
> > Last week, I disabled the ability of propset to take a value from a
> > file. The current usage of it is:
> > $ svn propset key value
> > Now before I dedicate any more of my (limited) brain power to thinking
> > about how we can best do this (given the current arg parsing
> > mechanism), let me ask you: Does this function *really* need to get a
> > property value from a file?
> Property values are binary strings (svn_string_t), not null-delimited
> text strings.
> Think about the kinds of things you'd store in a Mac HFS resource
I'd rather not. Resource forks give me the willies. :)
> File type, which application "owns" the file, and perhaps an
> icon... and icons are binary graphics files. Even Win32 executables
> store icons as internal `properties' this way.
> So I think it's convenient for the user to be able to store a binary
> file in a property value. It could be an icon, a self-portrait, a
> non-asciified public key, whatever.
Ahh. Now I understand your intent (although I must say that I don't
know that this is a feature that most (or even more than a few) people
would use, but that's probably just the CLI in me talking.
I'll get back to fixing what I broke.
Received on Sat Oct 21 14:36:25 2006