Activity log for bug #302302
| Date | Who | What changed | Old value | New value | Message |
|---|---|---|---|---|---|
| 2008-11-26 06:15:01 | Joshua Cronemeyer | bug | added bug | ||
| 2009-01-02 05:45:31 | Joshua Cronemeyer | shellsink: importance | Undecided | High | |
| 2009-01-02 05:45:31 | Joshua Cronemeyer | shellsink: statusexplanation | |||
| 2009-02-07 13:52:23 | Joshua Cronemeyer | shellsink: status | New | In Progress | |
| 2009-02-07 13:52:23 | Joshua Cronemeyer | shellsink: assignee | joshuacronemeyer | ||
| 2009-02-07 13:52:23 | Joshua Cronemeyer | shellsink: statusexplanation | This is a priority for me. Especially since I went and announced the existance of shell sink, somebody else might use the thing and you should be able to figure out what is going wrong. | ||
| 2009-02-14 15:24:23 | Joshua Cronemeyer | shellsink: status | In Progress | Fix Committed | |
| 2009-02-14 15:24:23 | Joshua Cronemeyer | shellsink: statusexplanation | This is a priority for me. Especially since I went and announced the existance of shell sink, somebody else might use the thing and you should be able to figure out what is going wrong. | Revision 36 make shellsink log to syslog instead of just printing errors to std. out. I'm not sure if there should be a visual indicator that shellsink is having problems yet. Perhaps that should be configurable? I'm going to think about it this weekend and see what I can come up with. |
