b2438ddb2c
prep for future dev
2013-01-29 00:00:35 -08:00
6de3e42180
prepare for 0.18.2 release
2013-01-29 00:00:16 -08:00
573c33ab99
changelog for recent stuff; 'DEBUG' was a dumb name for this internal var
2013-01-29 00:00:04 -08:00
0a39334d3c
prep for future dev
2013-01-22 17:33:47 -08:00
3b66127053
prepare for 0.18.1 release
2013-01-22 17:33:02 -08:00
d1baeb197e
some cases to not page automatically
2013-01-22 17:27:30 -08:00
acfe28bffe
prep for future dev
2013-01-22 17:00:14 -08:00
2dee5dcf96
prepare for 0.18.0 release
2013-01-22 17:00:14 -08:00
b1c143c87a
bunyan CLI auto-paging
2013-01-18 21:24:23 -08:00
bd4dec5bec
move test suite to nodeunit
2013-01-07 11:18:12 -08:00
e04f574f55
prep for future dev
2013-01-04 14:32:34 -08:00
6f83138c8d
prepare for 0.17.0 release
2013-01-04 14:32:19 -08:00
61fa82e704
note that log rotation support was for issue #33
2013-01-04 14:31:02 -08:00
480ee5d1e0
log rotation support; v0.17.0; improve README docs
2013-01-04 14:30:27 -08:00
cf38811126
don't special case 'latency' in default CLI rendering of log records
2012-12-27 13:21:56 -08:00
74d3935348
exit on EPIPE to avoid useless work
2012-12-18 16:34:40 -08:00
c5bfdc4cf3
prep for future dev
2012-12-14 11:48:56 -08:00
e52989d3f2
prepare for 0.16.8 release
2012-12-14 11:48:40 -08:00
cfdb30e105
guards and UX for -c CONDITION usage
2012-12-14 11:47:38 -08:00
9acc97ed7f
prep for future dev
2012-11-14 22:42:11 -08:00
5210c66a08
prepare for 0.16.7 release
2012-11-14 22:41:50 -08:00
c05f7cdfdb
don't break 'make versioncheck'
2012-11-14 22:41:41 -08:00
04583ab425
known issue
2012-11-14 22:40:37 -08:00
70f8d4d4da
[issue #59 ] Clear a possibly interrupted ANSI color code on signal termination.
2012-11-14 19:27:53 -08:00
af002db218
prep for future dev
2012-11-13 00:19:42 -08:00
b5c0f7f169
prepare for 0.16.6 release
2012-11-13 00:19:22 -08:00
f08c2e6f2c
issue #56 : bunyan -p NAME
2012-11-13 00:12:57 -08:00
9d7bd77c76
prep for future dev
2012-11-06 12:55:57 -08:00
262e4f4e79
prepare for 0.16.5 release
2012-11-06 12:55:27 -08:00
918c8081ca
bunyan -p '*'
2012-11-06 12:55:02 -08:00
6869931a60
issue #55 : add BUNYAN_NO_COLOR envvar support
2012-11-06 12:50:39 -08:00
3869ee308c
prep for future dev
2012-11-04 22:13:34 -08:00
0bddaeb060
prepare for 0.16.4 release
2012-11-04 22:12:59 -08:00
69285c7a79
issue #54 : fix stderr flushing of dtrace child proc (again)
2012-11-04 22:11:55 -08:00
7166772533
prep for future dev
2012-11-02 13:44:27 -07:00
59df6b2186
prepare for 0.16.3 release
2012-11-02 13:44:10 -07:00
da55eeee60
back to dtrace-provider dep
2012-11-02 13:36:46 -07:00
7e20b2d988
prep for future dev
2012-11-02 13:29:19 -07:00
b453eb81e7
prepare for 0.16.2 release
2012-11-02 13:28:29 -07:00
44fc428a8a
ensure dtrace stderr is piped through
2012-11-02 13:27:58 -07:00
d133deff82
prep for future dev
2012-11-02 12:16:11 -07:00
4013f7ad94
prepare for 0.16.1 release
2012-11-02 12:15:47 -07:00
4d0f6aeb96
ensure termination of child dtrace on CLI term by a signal
2012-11-02 12:15:29 -07:00
77b556d245
prep for future dev
2012-11-01 23:50:12 -07:00
8d67988be3
prepare for 0.16.0 release
2012-11-01 23:49:56 -07:00
79e5ded839
'bunyan -p PID' support
2012-11-01 23:49:09 -07:00
899a3420cf
better pitch for the dtrace support
2012-11-01 13:19:30 -07:00
c277e1d15d
prep for future dev
2012-11-01 13:14:08 -07:00
7a62928dfb
prepare for 0.15.0 release
2012-11-01 13:13:51 -07:00
8732764c67
issue #48 : changelog, add Bryan to AUTHORS, basic dtrace test suite
...
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.
2012-10-31 23:52:53 -07:00
Trent Mick