Macs have had type info separate from the file name for years. One of the
things I like about subversion is that it has the properties to store this
meta-data. Subversion should use these properties rather than dumping all
the file meta-data into the file name. After all, that is what the
properties are there for. If you want to waste some time :), have a read
On 15/3/02 6:38 PM, "Bill Tutt" <firstname.lastname@example.org> wrote:
> I thought about using MIME type, but that adds additional issues like
> storing the MIME type <-> file pattern mapping information, versioning
> that, etc...
I would imagine that setting the svn:mime-type would only happen when a file
is added. It would be a client function. The mapping info would be stored
in the ~/.subversion directory. It could be versioned the same way any
other info in that directory can be. To throw out a simple example file
Note that the first argument in the list is the mime type. This is because
the mime type doesn't have spaces or other weird characters - I suspect it'd
be easier to parse that way.
This adds the ability for "binaryness" to be detected by filename pattern
too :). I'm currently versioning some diagrams for my thesis that keep
being seen as text when they're really binary.
> Additionally, the way Subversion currently records that a file is being
> treated as binary tweaks the MIME type property. This seems completely
> backwards, just set a property that says it's binary and get on with it.
Not backwards, although not fully featured yet. I agree that this would
need to be improved, as demonstrated above, before you could use the
svn:mime-type property. I think getting rid of the svn:mime-type property
would be a mistake.
I wish I had time to submit patches :(
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Sat Mar 16 01:17:53 2002