In the 'Additional Information' section, we humble bug submitters are instructed that "Any information longer than a few lines [...] should be added using the "Create a new Attachment" link on the bug, after it is filed. OK, no pasting my entire customized linux kernel source code as 'additional information' -- seems intelligent enough. However, just below is a new instruction: "Please paste all information from 'emerge info' in this section!" Okay, but I was just instructed *not* to paste any lengthy information! Should I a) ignore instruction #1 in this case, obey #2 and paste the emerge info b) obey instruction #1, reinterpret instruction #2 (not taking the 'paste' part so literally) and attach the emerge info as an attachement c) stop worrying So which one is it? :) Personally I would consider (after c, naturally) b to be the best choice, since this way the bug report would perhaps be more readable. Reproducible: Always Steps to Reproduce: 1. Do not paste lengthy information 2. Paste lengthy information 3. ERROR BEEP BEEP *crash*
seems pretty obvious to me. 'any additional information' would be an 'emerge info', where as an attachment coudl be used for a stack trace as described, or maybe some sort of long log output.
