You may find mentions of "crashes" in the old documentation, but we prefer
We have been trying to move from "crashes" to "problems" since we
It's a never ending story. One has to think a lot before introducing a new
---------- Původní zpráva ----------
Od: Andreas Nilsson <lists(a)andreasn.se>
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, jfilak(a)fedoraproject.org wrote:
>> Wow, the design looks cool.
>> One comment: Are you sure you want to use the terms "Crash" and
>> 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 
>> - ABRT Java connector can be configured to report also caught exceptions
> I'm not married to that term at all. What's a better name for it?
> "Errors", "Irregularities"?
What does the documentation (RHEL/Fedora) usually refer to abrt objects as?
cockpit-devel mailing list -- cockpit-devel(a)lists.fedorahosted.org
To unsubscribe send an email to cockpit-devel-leave(a)lists.fedorahosted.org