From: Adrian Bunk <bunk@stusta.de>
To: Pavel Machek <pavel@suse.cz>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.6.16.28-rc2
Date: Thu, 24 Aug 2006 15:36:53 +0200 [thread overview]
Message-ID: <20060824133653.GJ19810@stusta.de> (raw)
In-Reply-To: <20060824132039.GC7055@elf.ucw.cz>
On Thu, Aug 24, 2006 at 03:20:39PM +0200, Pavel Machek wrote:
> Hi!
Hi Pavel!
> > Pavel Machek:
> > remove obsolete swsusp_encrypt
>
> Probably not a big deal, but IIRC this was cleanup patch. I am not
> sure if it is worth merging into -stable.
This patch removed an option that didn't have any effect.
IOW, less possible user confusion with no risk.
Additionally, the help text could wrongly imply for a user enabling this
option would bring additional security.
Not a big deal, but my personal opinion was to merge it.
> Pavel
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
prev parent reply other threads:[~2006-08-24 13:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-22 23:01 Linux 2.6.16.28-rc2 Adrian Bunk
2006-08-23 2:23 ` Grant Coady
2006-08-23 8:06 ` Stefan Richter
2006-08-23 20:05 ` Adrian Bunk
2006-08-24 13:20 ` Pavel Machek
2006-08-24 13:36 ` Adrian Bunk [this message]
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=20060824133653.GJ19810@stusta.de \
--to=bunk@stusta.de \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
/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