Skip to content

Commit

Permalink
Doc changes
Browse files Browse the repository at this point in the history
  • Loading branch information
jwegan committed Feb 26, 2013
1 parent e00b985 commit bd68962
Show file tree
Hide file tree
Showing 2 changed files with 3 additions and 2 deletions.
1 change: 1 addition & 0 deletions CHANGES
@@ -1,2 +1,3 @@
v0.1.3 2013-02-20 -- Log values of all variables in stack frame at time of the exception
v0.1.2 2013-02-10 -- Minor bug fixes & documentation updates
v0.1, 2013-02-06 -- Initial release
4 changes: 2 additions & 2 deletions README.md
Expand Up @@ -19,8 +19,8 @@ Why You Should Use Flawless
* Only emails 1 developer. Flawless uses git-blame to figure out which developer is responsible
for a particular exception, and will only email that developer.

* Flawless reports the values of each variable in the stack at the time the exception occurred.
This makes debugging ten times faster.
* Flawless logs the values of every variable in the stack frame at the time the exception
occurred. This makes debugging ten times faster.

* Don't report exceptions in old code. If you set report\_only\_after\_minimum\_date, then
Flawless will only report exceptions caused by code modified after
Expand Down

0 comments on commit bd68962

Please sign in to comment.