public inbox for cip-dev@lists.cip-project.org
 help / color / mirror / Atom feed
From: ben.hutchings@codethink.co.uk (Ben Hutchings)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] Introduction
Date: Wed, 14 Sep 2016 12:10:40 +0100	[thread overview]
Message-ID: <1473851440.4719.37.camel@codethink.co.uk> (raw)

I've been asked to introduce myself to the list, before getting into
discussions.  So here's a very brief summary.

I've been working on the Linux kernel for about 10 years, including
co-maintenance of Debian's kernel package for most of that time.  Debian
provides security support for each stable release for 5 years, and in
support of that I backported many fixes to 2.6.32-longterm and took on
maintenance of the 3.2-longterm and 3.16-longterm branches.

I'm now adding another part-time role as lead kernel maintainer for the
CIP.  I look forward to working with you all to establish a project and
process that can extend the support lifetime even further.

Ben.

-- 
Ben Hutchings
Software Developer, Codethink Ltd.

             reply	other threads:[~2016-09-14 11:10 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-14 11:10 Ben Hutchings [this message]
2016-09-15  6:50 ` [cip-dev] Introduction Daniel Sangorrin
2016-09-15  8:30   ` Agustin Benito Bethencourt
2016-09-15 10:05     ` Domenico Andreoli
2016-09-15 16:17     ` Paul Sherwood
2016-09-15 16:44       ` Paul Sherwood
2016-09-15 22:31       ` Ben Hutchings
2016-09-16  5:03         ` Jan Kiszka
2016-09-16  5:15       ` Daniel Sangorrin
2016-09-16  7:40         ` Paul Sherwood
2016-09-16  9:24           ` Daniel Sangorrin
2016-09-16  0:45     ` Daniel Sangorrin
2016-09-16  7:53     ` KOBAYASHI Yoshitake
2016-09-24 12:50       ` Gleim, Urs
2016-09-15 12:12 ` Noriaki Fukuyasu

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=1473851440.4719.37.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