Andrew Pinski wrote: >>[Danny, see below for a request.] >> >>In my review of open PRs against the 4.1 branch, I'm going to adopt a >>new convention. >> >>Until now, when I've decided something is not important enough to >>require fixing for a particular release, I unset the target milestone. >>That's confusing because it might seem to mean that I'm saying the bug >>*can't* be fixed for a particular release, which isn't true. > > > It might be better to add a flag for this istead of using the priority > field.
I think it's an appropriate use of the priority field; the priority field is supposed to say how important the bug is, which is another way of saying how excited we should be about fixing it in an upcoming release. -- Mark Mitchell CodeSourcery, LLC [EMAIL PROTECTED] (916) 791-8304
