<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Jan 29, 2012, at 9:54 PM, Jason Switzer wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">Hi, my name is Jason Switzer and I have been wanting to help out with LLVM for some time. I decided to start by going through the bug database and doing some wrangling (updating, verifying current behavior versus reported, etc) as it seemed like the easiest way to learn the code base. </blockquote><div><br></div><div>Awesome, this is definitely welcome. I bet there is a lot of stuff in the database that is either dupable, already fixed, or doesn't make sense anymore.</div><br><blockquote type="cite"><div><div>This bug was reported 2.5 years ago and hasn't seen a status change in 2 years. I don't feel right changing the status of this without someone else at least seeing it and I'm afraid any email that bugzilla would send might get overlooked by those that could do meaningful review.</div></div></blockquote><div><br></div><blockquote type="cite"><div>
</div><div>So what's the current LLVM / Clang way of dealing with this? As a someone who's just getting started with LLVM, I'd like to help, but I would hate to pump a ton of time going through a bunch of bugs only to have my help/feedback ignored. Should I double post my comments (<a href="http://llvm.org/bugs">llvm.org/bugs</a> and cfe-dev)? I'm guessing that if I have a patch to make, I should post it to cfe-commits, but I am afraid that such small issues/changes might get lost there as well.</div>
</blockquote><br></div><div>The best thing to do here is to use your judgement. If it seems that something is obviously fixed, just close it as fixed and someone can reopen it. If you think something is questionable or wrong minded, feel free to post a comment in the bug or bring it to cfe-dev. Any work here is really appreciated, so I don't think anyone will be annoyed with you asking questions :)</div><div><br></div><div>-Chris</div><br></body></html>