jQuery: added typing for fn
Support multiple 'from' states

According to https://github.com/jakesgordon/javascript-state-machine:
"If an event is allowed from multiple states, and always transitions to the same state, then simply provide an array of states in the from attribute of an event."

So the from property can be of type string or string[], so "any" is required here.
update to EaselJS v0.7.1.
Added property for query string parameters

Property qs for SignalR connection could be used to pass additional parameters to new SignalR persistent/hub connections. It is available since 1.0 and is present in 2.0 version of SignalR
append the author's name in the definition file.
Merge pull request #1575 from gyohk/EaselJS-0.7.1

update to EaselJS v0.7.1.
Fixed some typings with the chain syntax
Merge pull request #1580 from kant2002/master

Added property for query string parameters
Underscore: Used tabs vs spaces for my additions

and added explanation in test
Merge branch 'master' of https://github.com/borisyankov/DefinitelyTyped.git
Add new "silent" setting to AreYouSureOptions

Add new "silent" setting to AreYouSureOptions
Add optional 'message' parameter to chai.expect.

As noted at http://chaijs.com/guide/styles/#expect:

    "Expect also allows you to include arbitrary messages
     to prepend to any failed assertions that might occur."
Full WinJS and WinRT update

This contains a complete WinJS type definition with required WinRT type
definition update.
WinJS file heading

Re-added license and WinRT reference.
es6-promises fix whitespace + argument names consistent with http://promises-aplus.github.io/promises-spec/
Merge pull request #1581 from tandyjames/master

Fixed some typings with the chain syntax - includes workaround for bug in TS 0.9.5.  Workaround will be removed when TS bug fix ships.
Added domready and domdelegate
jQuery: JSDoc Callbacks and tighten up typing
jQuery: back
jQuery: cater for jQuery.clientSideLogging

I haven't looked in detail at this but it looks that
jQuery.clientSideLogging is ill-advisedly clobbering ```$.error```.
This should probable be addressed at some point.