Skip to content

Conversation

jtpittman195
Copy link
Contributor

Currently there is no way to un-set the scope without having to
exit and re-enter crash. The ability to un-set can come in very
useful when running automated pykdump scripts and needing scope to
be cleared between script runs. Add the ability by allowing
'set scope 0' as a viable command.

Signed-off-by: John Pittman jpittman@redhat.com

Currently there is no way to un-set the scope without having to
exit and re-enter crash.  The ability to un-set can come in very
useful when running automated pykdump scripts and needing scope to
be cleared between script runs.  Add the ability by allowing
'set scope 0' as a viable command.

Signed-off-by: John Pittman <jpittman@redhat.com>
@k-hagio
Copy link
Contributor

k-hagio commented Jan 17, 2021

Thank you for the patch. But sorry, currently we do not accept Pull Requests from GitHub usually, we accept patches posted to the crash mailing list [1], because it has much more watchers than here. Could you post the patch to the list?

[1] https://www.redhat.com/mailman/listinfo/crash-utility

@jtpittman195
Copy link
Contributor Author

Absolutely. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants