From: Pavel Machek <pavel@ucw.cz>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: suspend-devel List <suspend-devel@lists.sourceforge.net>,
kix <kixdotes@users.sourceforge.net>,
pm list <linux-pm@lists.linux-foundation.org>,
stefan.seyfried@googlemail.com
Subject: Re: Help
Date: Wed, 23 Sep 2009 18:43:07 +0200 [thread overview]
Message-ID: <20090923164307.GA2092@elf.ucw.cz> (raw)
In-Reply-To: <200909230133.28689.rjw@sisk.pl>
Hi!
> > > > Message body follows:
> > > >
> > > > I would like to help in the project.
> > > >
> > > > - updating the database.
> > > >
> > > > Have you seen the patch I sent?
> > >
> > > Yes, sorry for the lack of response, but I didn't really have the time to
> > > review the patch.
> > >
> > > That said, I don't think we'd like to move the whitelist to a separate file.
> > > Rather than that, we've been considering removing it altogether.
> > >
> > > Still, if you want to maintain the whitelist in its current form, I think
> > > you could do that.
> >
> > Yes, maintainer for the whitelist would be very welcome.
> >
> > Now... whitelist inside the binary is very welcome for init=/bin/bash,
> > etc; OTOH if the .c file is compiled from .txt description... that's
> > probably acceptable. Also it might make sense to load external
> > whitelist _in addition_ to the internal one, so people can quickly
> > experiment with whitelist entries...
>
> If you're still willing to be a whitelist maintainer, please set up a git
> repository from which I can pull the whitelist updates.
Yes, that would be great.
> If you'd like to move the whitelist to a separate file, please do so. You are
> free to use whatever format you think is suitable, although it would be nice
> if the whitelist file could be easily updated by users.
Ack.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2009-09-23 16:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1McOLX-0003Lq-BN@665xhf1.ch3.sourceforge.com>
[not found] ` <200908152239.15915.rjw@sisk.pl>
[not found] ` <20090822073516.GD2108@elf.ucw.cz>
2009-09-22 23:33 ` Help Rafael J. Wysocki
[not found] ` <200909230133.28689.rjw@sisk.pl>
2009-09-23 8:34 ` [Suspend-devel] Help Rodolfo (kix)
2009-09-23 16:43 ` Pavel Machek [this message]
[not found] ` <3096bd910909230134v6ad1c5acr53b172d9472488e8@mail.gmail.com>
2009-09-23 22:28 ` Rafael J. Wysocki
[not found] ` <200909240028.03305.rjw@sisk.pl>
2009-09-24 12:51 ` Stefan Seyfried
[not found] ` <20090924145128.26e758df@strolchi.home.s3e.de>
2009-09-24 17:53 ` Rafael J. Wysocki
[not found] ` <200909241953.46519.rjw@sisk.pl>
2009-09-24 18:20 ` Kix
[not found] ` <5B7CD99A-A3B3-44EC-A073-31C0A5B7286B@gmail.com>
2009-09-28 22:13 ` Rodolfo (kix)
[not found] ` <3096bd910909281513h134e505cy6631f998cd1cba5b@mail.gmail.com>
2009-09-28 22:27 ` Rafael J. Wysocki
[not found] ` <200909290027.08115.rjw@sisk.pl>
2009-09-28 22:57 ` Kix
[not found] ` <3A45B297-68FA-461E-9E31-864627534050@gmail.com>
[not found] ` <200910041524.42266.rjw@sisk.pl>
2009-11-11 11:22 ` Rodolfo (kix)
[not found] ` <3096bd910911110322w744a184cj99bf442d5baca1a2@mail.gmail.com>
2009-11-11 11:32 ` Rafael J. Wysocki
[not found] ` <200911111232.27309.rjw@sisk.pl>
2009-11-11 11:33 ` Rodolfo (kix)
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=20090923164307.GA2092@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=kixdotes@users.sourceforge.net \
--cc=linux-pm@lists.linux-foundation.org \
--cc=rjw@sisk.pl \
--cc=stefan.seyfried@googlemail.com \
--cc=suspend-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