From c9120cdc51ce7aba5a19500bf24692144ac64983 Mon Sep 17 00:00:00 2001 From: Denys Vlasenko Date: Tue, 10 May 2011 02:08:58 +0200 Subject: Do away with reanalyze events Now code determines whether analyze event can be skipped by looking at backtrace element in .xml file. Signed-off-by: Denys Vlasenko --- doc/design | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'doc') 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. -- cgit