Hello everyone! I'm new to open-source in general and to LLVM in particular. I'd like to contribute and was thinking of starting from http://llvm.org/bugs/show_bug.cgi?id=5639 What the next step should be? Should I register somewhere? Thanks, Tami -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20100512/261df9a0/attachment.html>
Welcome Tami. Tan4ik <tan4ik at gmail.com> writes:> I'm new to open-source in general and to LLVM in particular. > I'd like to contribute and was thinking of starting from > http://llvm.org/bugs/show_bug.cgi?id=5639 > What the next step should be? Should I register somewhere?No need to register. Be sure to carefully read http://www.llvm.org/docs/DeveloperPolicy.html then go ahead with your task, make a patch as described on the above mentioned document, and send it to the llvm-commits mailing list for review. Happy LLVM hacking!
On Wed, May 12, 2010 at 10:55 AM, Tan4ik <tan4ik at gmail.com> wrote:> I'm new to open-source in general and to LLVM in particular. > I'd like to contribute and was thinking of starting from > http://llvm.org/bugs/show_bug.cgi?id=5639 > What the next step should be? Should I register somewhere? >1. Register for an account at the LLVM Bugzilla (the link you sent above). 2. Find a bug to work on (as you've done already) 3. Accept the bug to show that you're working on it, so that effort isn't duplicated 4. Post a patch (and test case, if applicable) that fixes the bug 5. Respond to feedback and iterate to revise your patch as needed, until someone accepts and submits your patch 6. Mark bug as "fixed" 7. Repeat from step 2 Misha -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20100512/4637a99b/attachment.html>
Great! Thank you Tami On Wed, May 12, 2010 at 10:26 AM, Misha Brukman <brukman at gmail.com> wrote:> On Wed, May 12, 2010 at 10:55 AM, Tan4ik <tan4ik at gmail.com> wrote: > >> I'm new to open-source in general and to LLVM in particular. >> I'd like to contribute and was thinking of starting from >> http://llvm.org/bugs/show_bug.cgi?id=5639 >> What the next step should be? Should I register somewhere? >> > > 1. Register for an account at the LLVM Bugzilla (the link you sent above). > 2. Find a bug to work on (as you've done already) > 3. Accept the bug to show that you're working on it, so that effort isn't > duplicated > 4. Post a patch (and test case, if applicable) that fixes the bug > 5. Respond to feedback and iterate to revise your patch as needed, until > someone accepts and submits your patch > 6. Mark bug as "fixed" > 7. Repeat from step 2 > > Misha >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20100512/6d218d7c/attachment.html>
Apparently Analagous Threads
- [LLVMdev] would like to contribute
- df does not show full volume capacity after update to 3.12.4
- df does not show full volume capacity after update to 3.12.4
- df does not show full volume capacity after update to 3.12.4
- df does not show full volume capacity after update to 3.12.4