From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: Joe Perches <joe@perches.com>
Cc: Peter Huewe <peterhuewe@gmx.de>,
tpmdd-devel@lists.sourceforge.net,
linux-ima-devel@lists.sourceforge.net,
linux-integrity@vger.kernel.org,
linux-security-module@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [tpmdd-devel] New ML for TPM and IMA
Date: Fri, 15 Sep 2017 14:47:13 -0700 [thread overview]
Message-ID: <20170915214713.qzg4pujpxzmy27bk@linux.intel.com> (raw)
In-Reply-To: <1505498511.27581.11.camel@perches.com>
On Fri, Sep 15, 2017 at 11:01:51AM -0700, Joe Perches wrote:
> On Fri, 2017-09-15 at 10:57 -0700, Jarkko Sakkinen wrote:
> > On Fri, Sep 15, 2017 at 10:47:06AM -0700, Peter Huewe wrote:
> > > Am 15. September 2017 10:40:14 GMT-07:00 schrieb Joe Perches <joe@perches.com>:
> > > > As the individual maintainers are different for the two sections,
> > > > I think you need both entries.
> > >
> > > Try to get a hold of ashley and ask whether she is actively maintaining.
> > >
> > > While updating Maintainers I vote for removing Marcel Selhorst for tpm.
> > >
> > > You can keep me for now :)
> > > Peter
> >
> > During the last bit less than couple of years I've been maintaining
> > TPM and a bit less than four years I've been contributing I've never
> > heard anything of Ashley.
> >
> > What is the expiration time?
>
> There is no fixed time at all.
> Generally when the email bounces or when the maintainer resigns.
> (involuntarily or not...)
>
> It seems a couple years since Ashley signed anything and five years
> since Marcel Selhorst signed anything.
>
> It's polite to add a CREDITS entry when removing inactive maintainers.
The file ends:
"
# Don't add your name here, unless you really _are_ after Marc
# alphabetically. Leonard used to be very proud of being the
# last entry, and he'll get positively pissed if he can't even
# be second-to-last. (and this file really _is_ supposed to be
# in alphabetic order)
"
So where do I should add?-)
/Jarkko
next prev parent reply other threads:[~2017-09-15 21:47 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-15 17:18 New ML for TPM and IMA Jarkko Sakkinen
2017-09-15 17:21 ` [tpmdd-devel] " Peter Huewe
2017-09-15 17:34 ` Jarkko Sakkinen
2017-09-15 17:25 ` Joe Perches
2017-09-15 17:36 ` Jarkko Sakkinen
2017-09-15 17:40 ` Joe Perches
2017-09-15 17:47 ` [tpmdd-devel] " Peter Huewe
2017-09-15 17:57 ` Jarkko Sakkinen
2017-09-15 18:01 ` Joe Perches
2017-09-15 21:47 ` Jarkko Sakkinen [this message]
2017-09-15 21:55 ` Joe Perches
[not found] ` <1505498511.27581.11.camel-6d6DIl74uiNBDgjK7y7TUQ@public.gmane.org>
2017-09-18 9:49 ` Marcel Selhorst
2017-09-15 20:07 ` [tpmdd-devel] " Ken Goldman
2017-09-15 20:32 ` Peter Huewe
[not found] ` <20170915171825.5zjit5vsrvxgmvrb-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2017-09-15 21:08 ` [Linux-ima-devel] " Ken Goldman
2017-09-15 21:44 ` Jarkko Sakkinen
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=20170915214713.qzg4pujpxzmy27bk@linux.intel.com \
--to=jarkko.sakkinen@linux.intel.com \
--cc=joe@perches.com \
--cc=linux-ima-devel@lists.sourceforge.net \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=peterhuewe@gmx.de \
--cc=tpmdd-devel@lists.sourceforge.net \
/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).