Anant Narayanan <[EMAIL PROTECTED]> writes:
>>> We can also save the command history in a file so that the history is
>>> not lost after a session, athough this has nothing to do with command
>>> logging, may be we can consider this as a feature.
>> It would be *really* nice to automatically create a text file with
>> important information when a bug occurs. The user can then be
>> instructed to attach this to the bug he is reporting. Part of this file
>> should be command history, of course.
>
> Just committed a patch to show command history on crash. This will
> eventually go into a file. It would be cool to see if we can
> automatically create a Trac ticket if an internet connection is
> available (with users permission of course; like bug-buddy); otherwise
> we can ask the user to attach that file with the bug report.
>
> Thoughts on how the file should be named and where must we dump it
> (/tmp?) How about parted-YYYYMMDDHHMMSS.err? (timestamp)
I like the idea of a file on /tmp
Personally, automatically reported issues are difficult to solve since
usually we need more information about what the user was doing,
hardware information, request tests and like.
--
O T A V I O S A L V A D O R
---------------------------------------------
E-mail: [EMAIL PROTECTED] UIN: 5906116
GNU/Linux User: 239058 GPG ID: 49A5F855
Home Page: http://otavio.ossystems.com.br
---------------------------------------------
"Microsoft sells you Windows ... Linux gives
you the whole house."
_______________________________________________
parted-devel mailing list
[email protected]
http://lists.alioth.debian.org/mailman/listinfo/parted-devel
