Johan Corveleyn wrote:
> On Mon, Aug 24, 2009 at 9:29 AM, C. Michael Pilato<cmpilato_at_collab.net>
>> Yeah, I guess it would work fine if we set the svn:mime-type property
>> on our CHANGES file, though (to "text/plain"). *shrug*.
>> Extension-less files are always problematic for MIME type stuff. While
>> most of the extension-less files in our tree may be human-readable,
>> it's certainly conceivable that others would have extension-less files
>> in their trees that aren't human-readable. It's a win-lose situation!
> Note that not only extension-less files are affected currently. All the
> *.txt files under trunk/notes are also returned with "Content-Type:
> application/octet-stream", causing FF to popup its dialog to open or save
> the file.
Hrm. I thought that would only happen if a mime.types lookup failed to find
anything for .txt files. (Though, ISTR that this only works if Apache is so
configured, and I might not have svn.collab.net so configured.)
> Forgive my ignorance, but I don't really understand why this has changed.
> The old behavior was consistent with the way SVN considers files as
> text-files for diffing and merging. I.e. if a file has no mime-type svn
> will perform textual merges etc. (same as when it has a mime-type of
> text/*). Or am I wrong?
If by "this has changed", you mean "the code was touched at all", that was
due to an Apache API that we depended on going away.
If by "this has changed", you mean "the default of text/plain was changed
application/octet-stream", then I don't think gstein (who made the change,
and with good intent) actually realized he was changing an established default.
C. Michael Pilato <cmpilato_at_collab.net>
CollabNet <> www.collab.net <> Distributed Development On Demand
Received on 2009-08-27 00:06:31 CEST