From: Radjino Bholanath <R.M.R.Bholanath@student.tudelft.nl>
To: "gdb@sourceware.org" <gdb@sourceware.org>
Subject: Questions about code reviews and static analysis tools for TU Delft research
Date: Tue, 24 Feb 2015 10:54:00 -0000 [thread overview]
Message-ID: <016900840D5AC640A0034E24ACD7F2600EE1931B@SRV366.tudelft.net> (raw)
Hi everyone,
I'm doing research on code reviews and static analysis tools at the SERG group (http://swerl.tudelft.nl/bin/view/Main/WebHome) of the Delft University of Technology. Currently, we want to give an overview of the usage of code review and static analysis tools in open source projects. Therefore, I would be very happy to know a little bit more about how code reviews are used in GDB and if (and maybe how) static analysis tools are used. I have a couple of questions for anyone willing to answer:
1. Do all developers (contributors and core developers) have to submit a code review for every change? I’m asking because many projects only review changes made by contributors.
2. Which code review tools are used?
3. Are static analyzers used? If they are used:
a. Is passing the checks of the static analyzers necessary for a change to be accepted?
b. Which static analyzers are used?
Thanks,
Radjino
next reply other threads:[~2015-02-24 10:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-24 10:54 Radjino Bholanath [this message]
2015-02-25 23:21 ` Joel Brobecker
2015-02-25 23:36 ` Radjino Bholanath
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=016900840D5AC640A0034E24ACD7F2600EE1931B@SRV366.tudelft.net \
--to=r.m.r.bholanath@student.tudelft.nl \
--cc=gdb@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox