Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
Commits on Nov 15, 2012
  1. prepare for 0.16.7 release

    authored
  2. don't break 'make versioncheck'

    authored
  3. known issue

    authored
Commits on Nov 13, 2012
  1. prep for future dev

    authored
  2. prepare for 0.16.6 release

    authored
  3. issue #56: bunyan -p NAME

    authored
Commits on Nov 6, 2012
  1. prep for future dev

    authored
  2. prepare for 0.16.5 release

    authored
  3. bunyan -p '*'

    authored
Commits on Nov 5, 2012
  1. prep for future dev

    authored
  2. prepare for 0.16.4 release

    authored
Commits on Nov 2, 2012
  1. prep for future dev

    authored
  2. prepare for 0.16.3 release

    authored
  3. back to dtrace-provider dep

    authored
  4. prep for future dev

    authored
  5. prepare for 0.16.2 release

    authored
  6. prep for future dev

    authored
  7. prepare for 0.16.1 release

    authored
  8. prep for future dev

    authored
  9. prepare for 0.16.0 release

    authored
  10. 'bunyan -p PID' support

    authored
Commits on Nov 1, 2012
  1. prep for future dev

    authored
  2. prepare for 0.15.0 release

    authored
  3. issue #48: changelog, add Bryan to AUTHORS, basic dtrace test suite

    authored
    The test suite for this is a bit finnicky because root rights are
    required to run dtrace. By default we run the dtrace.test.js file
    with 'sudo'. Use this to skip the dtrace tests:
        SKIP_DTRACE=1 make test
    
    Note taht 'make test09' is busted because dtrace-provider seems
    busted with node 0.9.1 at least.
  4. issue #48: make dtrace-provider presence optional (disabled dtrace pr…

    authored
    …obes)
    
    dtrace-provider is still in *dependencies* to strongly encourage
    installing it. However I want bunyan.js to be useable for basic
    usage standalone.
  5. issue #48: fix a couple issues with dtrace support

    authored
    - before this, if there were no non-raw streams on the logger the
      `str` for the dtrace probe.fire would not be created
    - ensure that with no non-raw streams we only render a record's
      JSON string if the dtrace probe is enabled
Something went wrong with that request. Please try again.