Julian Foad wrote:
> Here is a vision of a solution that doesn't treat MIME-type as "special"
> but can still take advantage of it, both for 99% "Do The Right Thing"
> without manual setting of another property, and also for backward
> compatibility.
>
> (1) Use of line-wise merge shall be determin
On Wed, Nov 18, 2009 at 08:25, David Glasser wrote:
> I'm not a MIME expert, but isn't there a thing where you can add
> key/value pairs after a MIME type which customize its meaning? Maybe
> that could be used for this?
Please, no.
Isn't the fact that charset is munged into svn:mime-type alread
I'm not a MIME expert, but isn't there a thing where you can add
key/value pairs after a MIME type which customize its meaning? Maybe
that could be used for this?
--dave
On Tue, Nov 17, 2009 at 7:05 PM, Julian Foad wrote:
> I need to spend some time replying, late at night though it is.
>
> Let
B. Smith-Mannschott wrote:
> After many years of using Subversion, I've come to the conclusion that
> svn:mime-type is best understood as a way to keep Apache happy and
> able to support read-only repository browsing. The fact that this
> property is also used to determine ability to merge, diff, a
David Glasser wrote:
> I'm not a MIME expert, but isn't there a thing where you can add
> key/value pairs after a MIME type which customize its meaning? Maybe
> that could be used for this?
>
I understand those attributes are defined by the RFC, and you can't just
add your own. You can add comm
5 matches
Mail list logo
