Re: possible bug in Mason 1.36

On Aug 21, 2007, at 12:00, Dave Rolsky wrote:

>> So how can we globally set it again?
>
> Globally set the content type, you mean?

Yes.

> My point was simply that while I don't understand how this code  
> worked with Mason 1.35, there's no reason it shouldn't continue to  
> work with 1.36 ;)

Um, the reverse is true, as David Beaudet pointed out.

Best,

David

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/