added a synchronous file appender
added tests for the fileSync appender and changed the behavior of fileSync to create an empty log when called, just like the file appender does
fixed a issue with the encoding on node 0.8
Stop making use of any layout

Stop making use of any layout by default, because they are intended to
format a line for human reading. Loggly indexes the values (of all
properties of objects) and makes them available for querying.
Set the global level via the configuration object passed to
log4js.configure or target `all` in the `levels` object.
Changed to only the ‚levels’ option as discussed in #87
Update log4js.js

Overlooked that there was already a var with '[all]'.
Allow adding of appenders as objects

Previously, appenders could only be added by specifying the filepath
to the appender. This required the appender's path to be specified
either relative to the log4js installation, relative to a NODE_PATH
token, or absolute. This creates a coupling between the log4js
configurer and the log4js installation location, or a coupling between
the log4js configurer and the global NODE_PATH. This commit removes
the coupling by allowing the loading of appenders to be done relative
to the log4js configurer.
Simplied loadAppender logic.
Add unit test to check if the level is set on all categories
Update for "write after end" uncaught error.
removed check for writeable

caused broken unit tests
epic day with a forgotten console
Merge pull request #209 from Icehunter/patch-1

Update for "write after end" uncaught error.
Merge pull request #203 from idalv/master

Clusterred appender should consider the categories.
Merge pull request #189 from jengler/add-support-for-prerequired-appender-styles

Add support for prerequired appender styles
Merge pull request #175 from devotis/master

Loggly appender should not make use of any layout
0.6.15
Added link to example app.
GELF appender: don't send full_message field

According to the GELF spec v1.1 [1], the full_message field in GELF is
optional. The log4js implemention until now has sent identitical
short_message and full_message fields. Since this does not add any new
information to the log message, I suggest that full_message be dropped
from GELF.

--
[1] http://graylog2.org/gelf#specs