From: Roman Suvorov <4rvs19@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: kernel builds
Date: Wed, 18 Apr 2012 01:13:58 -0400 [thread overview]
Message-ID: <3B7A3118-B3CE-4B67-8A86-CA5CB41105FE@gmail.com> (raw)
Hello everyone,
I'm a graduate student doing some research on the build systems of large open-source projects. I was wondering how often developers recompile the entire kernel to test the changes they make to the source code (be those new features or bug fixes)?
Please CC me when you reply, much appreciated.
Thank you,
Roman.
next reply other threads:[~2012-04-18 5:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-18 5:13 Roman Suvorov [this message]
[not found] <4F8E77B7.1030201@web.de>
2012-04-18 20:16 ` Kernel Builds Roman Suvorov
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=3B7A3118-B3CE-4B67-8A86-CA5CB41105FE@gmail.com \
--to=4rvs19@gmail.com \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®