summaryrefslogtreecommitdiffstats
path: root/doc
diff options
context:
space:
mode:
authorDenys Vlasenko <dvlasenk@redhat.com>2011-05-10 02:08:58 +0200
committerDenys Vlasenko <dvlasenk@redhat.com>2011-05-10 02:08:58 +0200
commitc9120cdc51ce7aba5a19500bf24692144ac64983 (patch)
tree0ea3eea23f1f68bca3b40e50e64616e7885b5d75 /doc
parent752b264ed8b08a59e60894b310bad522585674e9 (diff)
downloadabrt-c9120cdc51ce7aba5a19500bf24692144ac64983.tar.gz
abrt-c9120cdc51ce7aba5a19500bf24692144ac64983.tar.xz
abrt-c9120cdc51ce7aba5a19500bf24692144ac64983.zip
Do away with reanalyze events
Now code determines whether analyze event can be skipped by looking at <creates-elements>backtrace</creates-elements> element in .xml file. Signed-off-by: Denys Vlasenko <dvlasenk@redhat.com>
Diffstat (limited to 'doc')
-rw-r--r--doc/design4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/design b/doc/design
index 5da16cc2..05a96cdd 100644
--- a/doc/design
+++ b/doc/design
@@ -71,8 +71,8 @@ can trigger their initial ("post-create") processing themselves]
Crashes conceptually go through "events" in their lives.
Apart from "post-create" event decribed above, they may have
-"analyze" event, "reanalyze" event, "report[_FOO]" events,
-ans arbitrarily-named other events.
+"analyze" event, "report[_FOO]" events,
+and arbitrarily-named other events.
abrt-handle-crashdump tool can be used to "run" an event on a directory,
or to query list of possible events for a directory.
/etc/abrt/abrt_event.conf file describes what should be done on each event.