From: agustin.benito@codethink.co.uk (Agustín Benito Bethencourt)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] Evaluation of the code review from Moxa so far
Date: Thu, 07 Jun 2018 17:10:10 +0200 [thread overview]
Message-ID: <1862979.Hem8Rly24N@linux-if6s> (raw)
Hi SZ Lin,
it would be useful for us and also for the coming TSC meeting at OSSJ if you
could provide to this list a report about the experience of Moxa devs reviewing
stable kernel patches, including the challenges and the highlights.
Do you think is this a good idea? Is it doable before the OSSJ 2018?
Best Regards
--
Agust?n Benito Bethencourt
Principal Consultant
Codethink Ltd
We respect your privacy. See https://www.codethink.co.uk/privacy.html
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.cip-project.org/pipermail/cip-dev/attachments/20180607/11fe0b9d/attachment.html>
next reply other threads:[~2018-06-07 15:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-07 15:10 Agustín Benito Bethencourt [this message]
2018-06-07 16:35 ` [cip-dev] Evaluation of the code review from Moxa so far SZ Lin (林上智)
2018-06-08 4:50 ` Agustin Benito Bethencourt
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=1862979.Hem8Rly24N@linux-if6s \
--to=agustin.benito@codethink.co.uk \
--cc=cip-dev@lists.cip-project.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