kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: mueddib@goosey.org (Ozgur Karatas)
To: kernelnewbies@lists.kernelnewbies.org
Subject: kernel development process question, patch review
Date: Tue, 21 Feb 2017 20:32:12 +0300	[thread overview]
Message-ID: <274641487698332@web21h.yandex.ru> (raw)
In-Reply-To: <184861487698185@web28o.yandex.ru>


Hello,

I think the list idea is no need for confusion, it is desirable to provide people with a new kernel newbies update to this list with a help and a quick solution to their problems.
This is like pre-kernel training.

TO and CC already come with the get_maintainer.pl script.

TO: Primary responsible
CC: development group + kernel mailing list
Kernelnewbies = kernelnewbies help

Regards,

Ozgur

> 21.02.2017, 04:44, "Tobin C. Harding" <me@tobin.cc>:
>> ?If a reviewer makes a suggestion and one intends on making the change
>> ?as suggested is it required (normal protocol) to reply stating that
>> ?the you understand their suggestion and intend on implementing it or
>> ?is this just noise. Should one simply re send the next version of the
>> ?patch?
>>
>> ?Continuing on this theme, should one add a Suggested-by: tag in the
>> ?previous situation. Some where Documentation/process it states that no
>> ?tag except the CC tag should be added without the authority of the
>> ?person being named?
>>
>> ?thanks,
>> ?Tobin.

  reply	other threads:[~2017-02-21 17:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-21  1:35 kernel development process question, patch review Tobin C. Harding
2017-02-21  7:02 ` Greg KH
2017-02-21 17:29 ` Ozgur Karatas
2017-02-21 17:32   ` Ozgur Karatas [this message]
2017-02-21 19:40 ` valdis.kletnieks at vt.edu

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=274641487698332@web21h.yandex.ru \
    --to=mueddib@goosey.org \
    --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).