Hi guys, should we add a simple script like below to scripts/ or so to use for cleaning up oopses before adding to commit messages?
Instead of doing all the work by hand and so on. It doesn't remove registers, stack and Code: lines yet but having it in the repo could be used to state exactly which pieces of the oops should go into a commit message and which not. We could even do editing on the oops itself for more readability and so on... Thoughts? --- #!/bin/sh sed --regexp-extended \ -e 's/\[\s+[0-9]+\.[0-9]+\]//' \ -e 's/\+[0-9x]+.*$//' \ -e 's/\[<.*>\]//' \ < "${1:-/dev/stdin}" -- Regards/Gruss, Boris. Good mailing practices for 400: avoid top-posting and trim the reply.