From: sebastien@masson.engineer (Sébastien Masson)
To: kernelnewbies@lists.kernelnewbies.org
Subject: What is the fastest way to build and boot a kernel
Date: Thu, 20 Apr 2017 10:21:49 +0200 [thread overview]
Message-ID: <c25f434734045599b8cd869f77f161df@masson.engineer> (raw)
In-Reply-To: <CABGNecwbM4c6ZHX=U6Y9jMtJDHhOSw47Ra136LxBnDKXQEiv1w@mail.gmail.com>
On 2017-04-19 20:26, Code Soldier1 wrote:
> On Wed, Apr 19, 2017 at 3:32 AM, Tobin C. Harding <me@tobin.cc> wrote:
>> On Tue, Apr 18, 2017 at 08:59:36AM -0700, Code Soldier1 wrote:
>> [snip]
>>
>> Why the moniker?
>
> Why not ? unlike most people today I value my privacy.
Hi!
In my opinion, the point is not really about privacy. Although, I
understand you concern.
As a kernel developer, the source code you will write will be subject to
copyright matters and, if you want to contribute, you will have to give
your agreement to this.
This is only possible using your real name.
I am inviting you to read: Documentation/process/submitting-patches.rst
in this regard.
Of course, as long as you do not submit source code, it does not really
matter. It may be more a question of "consistency".
BR,
Sebastien.
next prev parent reply other threads:[~2017-04-20 8:21 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-18 15:59 What is the fastest way to build and boot a kernel Code Soldier1
2017-04-18 16:07 ` Greg KH
2017-04-18 17:38 ` Code Soldier1
2017-04-18 17:42 ` Peter Senna Tschudin
2017-04-18 17:44 ` Greg KH
2017-04-18 18:04 ` Code Soldier1
2017-04-18 18:15 ` Guru Das S
2017-04-25 13:15 ` Manoj
2017-04-19 10:32 ` Tobin C. Harding
2017-04-19 10:49 ` valdis.kletnieks at vt.edu
2017-04-19 12:43 ` Aruna Hewapathirane
2017-04-19 18:26 ` Code Soldier1
2017-04-20 8:21 ` Sébastien Masson [this message]
2017-04-20 16:20 ` Code Soldier1
2017-04-20 16:31 ` Alexander Kapshuk
2017-04-20 16:54 ` Joe Smith
2017-04-20 17:50 ` Bjørn Mork
2017-04-20 19:27 ` Joe Smith
2017-04-21 8:43 ` Bjørn Mork
2017-04-19 11:24 ` Aruna Hewapathirane
2017-04-19 17:10 ` Stephen Brennan
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=c25f434734045599b8cd869f77f161df@masson.engineer \
--to=sebastien@masson.engineer \
--cc=kernelnewbies@lists.kernelnewbies.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;
as well as URLs for NNTP newsgroup(s).