You may find mentions of "crashes" in the old documentation, but we prefer
"problems".
We have been trying to move from "crashes" to "problems" since we introduced
kernel oopses.
It's a never ending story. One has to think a lot before introducing a new
term :)
Jakub
---------- Původní zpráva ----------
Od: Andreas Nilsson <[email protected]>
Komu: [email protected]
Datum: 28. 2. 2017 16:00:57
Předmět: Re: Supporting ABRT in Cockpit
"On 2017-02-28 14:01, Stephen Gallagher wrote:
> On 02/28/2017 05:40 AM, Andreas Nilsson wrote:
>> On 2017-02-28 10:57, [email protected] wrote:
>>> Wow, the design looks cool.
>>>
>>> One comment: Are you sure you want to use the terms "Crash" and
"Crashers"?
>>> Not every ABRT problem is a crash:
>>> - Python exceptions do not always cause a crash
>>> - Kernel oopses are not crashes at all
>>> - There might be other problem types like Eclipse ones [1]
>>> - ABRT Java connector can be configured to report also caught exceptions
[2]
>>>
>> I'm not married to that term at all. What's a better name for it?
"Problems",
>> "Errors", "Irregularities"?
> Anomalies?
What does the documentation (RHEL/Fedora) usually refer to abrt objects as?
- Andreas
_______________________________________________
cockpit-devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
"
_______________________________________________
cockpit-devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
