From: Andrew Morton <akpm@linux-foundation.org>
To: Trevor Highland <thighlan@gmail.com>
Cc: linux-kernel@vger.kernel.org,
ecryptfs-devel@lists.sourceforge.net, mhalcrow@us.ibm.com
Subject: Re: [PATCH] eCryptfs: Change the type of cipher_code from u16 to u8
Date: Wed, 19 Dec 2007 15:53:24 -0800 [thread overview]
Message-ID: <20071219155324.ad2ea045.akpm@linux-foundation.org> (raw)
In-Reply-To: <1198032282.6015.12.camel@buster2>
On Tue, 18 Dec 2007 20:44:42 -0600
Trevor Highland <thighlan@gmail.com> wrote:
> Change the type of cipher_code from u16 to u8.
I sure hope that Michael knows what's going on here, because these
changelogs aren't very useful. They tell us *what* the patch does (which
was pretty obvious anyway) but they don't tell use *why* it was done.
The patches were rather wordwrapped so a resend would be needed anyway
please. Some improved changelogging at the same time would be nice.
next prev parent reply other threads:[~2007-12-19 23:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-19 2:44 [PATCH] eCryptfs: Change the type of cipher_code from u16 to u8 Trevor Highland
2007-12-19 23:53 ` Andrew Morton [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-12-22 2:05 Trevor Highland
2007-12-18 6:24 Trevor Highland
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=20071219155324.ad2ea045.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=ecryptfs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mhalcrow@us.ibm.com \
--cc=thighlan@gmail.com \
/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