From: ben.hutchings@codethink.co.uk (Ben Hutchings)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] Kernel maintenance weekly meeting through IRC
Date: Wed, 18 Apr 2018 16:32:04 +0100 [thread overview]
Message-ID: <1524065524.2587.10.camel@codethink.co.uk> (raw)
In-Reply-To: <1605667.vNQfNKazDM@linux-if6s>
On Wed, 2018-04-18 at 16:58 +0200, Agust?n Benito Bethencourt wrote:
> Hi Ben,
>
> On Wednesday, 18 April 2018 16:52:16 CEST Ben Hutchings wrote:
> > On Mon, 2018-04-16 at 19:06 +0800, SZ Lin (???) wrote:
> > > Hi Ben,
> > >
> > > The following questions are which we want to know, please feel free to
> > > discuss with us.
> > >
> > > 1. CIP kernel maintenance team working model
> > >
> > > Do you have any suggested working model for CIP kernel maintenance team ?
> > > e.g., Debian kernel team (CPU architecture based) or upstream kernel
> > > (subsystem based)
> >
> > I think this would depend on how many developers would be working on it
> > (from all CIP members) and how much time they can devote.
> >
> > > 2. Hands-on tasks for team member
> > >
> > > We can start to review changes on the LTS branch; however, we would
> > > like to know if you have any preferred collaboration model for
> > > reviewing the results from team member.
> >
> > I think that developers who are used to doing public review of patches
> > should do that directly on the stable mailing list.??If you have
> > developers that don't have that experience, but want to start, then
> > they should initially send their review responses to an experienced
> > colleague or to me.
>
> In case the Moxa developers prefer you to mentor them for some time, should?
> they be looking into patches selected by them or do you have in mind some they?
> should start looking at?
I suggest looking at the most recent series sent out for review
(4.4.128). I can send this as a mailbox file for those who weren't
already susbcribed to the stable list.
Ben.
--
Ben Hutchings
Software Developer, Codethink Ltd.
next prev parent reply other threads:[~2018-04-18 15:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-03 9:01 [cip-dev] Kernel maintenance weekly meeting through IRC Agustín Benito Bethencourt
2018-04-11 17:43 ` SZ Lin (林上智)
2018-04-16 11:06 ` SZ Lin (林上智)
2018-04-18 14:52 ` Ben Hutchings
2018-04-18 14:58 ` Agustín Benito Bethencourt
2018-04-18 15:32 ` Ben Hutchings [this message]
2018-04-16 11:54 ` Jan Kiszka
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=1524065524.2587.10.camel@codethink.co.uk \
--to=ben.hutchings@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