Bug Helper

  1. Bug #81289
  2. Activity log

Activity log for bug #81289

Date Who What changed Old value New value Message
2007-01-24 15:17:38 Simon Law bug added bug
2007-01-24 15:17:51 Simon Law bughelper: status Unconfirmed Confirmed
2007-01-24 15:17:51 Simon Law bughelper: importance Undecided Wishlist
2007-01-24 15:17:51 Simon Law bughelper: statusexplanation
2007-01-24 15:59:59 Daniel Holbach bughelper: status Confirmed Needs Info
2007-01-24 15:59:59 Daniel Holbach bughelper: statusexplanation First of all: I agree with you - exporting the API of bughelper is a must and also we should have configurable output as well. Does bug 79142 cover what you're suggesting?
2007-02-12 13:28:31 Henrik Nilsen Omma bughelper: status Needs Info Rejected
2007-02-12 13:28:31 Henrik Nilsen Omma bughelper: statusexplanation First of all: I agree with you - exporting the API of bughelper is a must and also we should have configurable output as well. Does bug 79142 cover what you're suggesting? bughelper -p <packagename> --format=html > myfile.html already gives a good file that can be parsed. It doesn't provide all the information known about a bug, but bug helper doesn't look at all of it at this stage. We could of course add some more content to the html output version. What you may want is to use a bug number and go in a grab the entrire XML version of the bug from LP (when that feature becomes available). I doubt that implementing something short of that, yet more complete than the html dump is worth the effort.