mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Scott Preece" <sepreece@gmail.com>
To: "Satyam Sharma" <satyam.sharma@gmail.com>
Cc: "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
	"David Howells" <dhowells@redhat.com>,
	trivial@kernel.org
Subject: Re: [PATCH (trivial)] Fix typo in Documentation/keys.txt
Date: Thu, 7 Jun 2007 10:57:37 -0500	[thread overview]
Message-ID: <7b69d1470706070857n761b1358sfa41887f9ff83ecf@mail.gmail.com> (raw)
In-Reply-To: <a781481a0706070408qb5f13eexba0f7f80ef756cf9@mail.gmail.com>

On 6/7/07, Satyam Sharma <satyam.sharma@gmail.com> wrote:
> Fix a typo in Documentation/keys.txt.
>
> Signed-off-by: Satyam Sharma <ssatyam@cse.iitk.ac.in>
> Cc: David Howells <dhowells@redhat.com>
> Cc: trivial@kernel.org
>
> ---
>
>  Documentation/keys.txt |    5 ++---
>  1 file changed, 2 insertions(+), 3 deletions(-)
>
> ---
>
> diff -ruNp a/Documentation/keys.txt b/Documentation/keys.txt
> --- a/Documentation/keys.txt    2007-06-03 02:33:02.000000000 +0530
> +++ b/Documentation/keys.txt    2007-06-03 02:38:52.000000000 +0530
> @@ -859,9 +859,8 @@ payload contents" for more information.
>         void unregister_key_type(struct key_type *type);
>
>
> -Under some circumstances, it may be desirable to desirable to deal with a
> -bundle of keys.  The facility provides access to the keyring type for managing
> -such a bundle:
> +Under some circumstances, it may be desirable to deal with a bundle of keys.
> +The facility provides access to the keyring type for managing such a bundle:
---

It would improve the latter sentence to either delete "access to" or
else change "provides access to" to "defines.

scott

      parent reply	other threads:[~2007-06-07 15:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-07 11:08 Satyam Sharma
2007-06-07 15:51 ` David Howells
2007-06-07 15:57 ` Scott Preece [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=7b69d1470706070857n761b1358sfa41887f9ff83ecf@mail.gmail.com \
    --to=sepreece@gmail.com \
    --cc=dhowells@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=satyam.sharma@gmail.com \
    --cc=trivial@kernel.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

all inboxes | Powered by JetHome®