From: Randy Dunlap <rdunlap@infradead.org>
To: oscar@oscr.io
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
Jiri Kosina <trivial@kernel.org>
Subject: Re: [PATCH 1/1] Changed "&" with "and" in Documentation/applying-patches.txt.
Date: Thu, 25 Sep 2014 10:21:23 -0700 [thread overview]
Message-ID: <54244F13.2020202@infradead.org> (raw)
In-Reply-To: <1411652495-100852-1-git-send-email-oscar@oscr.io>
On 09/25/14 06:41, oscar@oscr.io wrote:
> From: Oscar Utbult <oscar@oscr.io>
>
> http://english.stackexchange.com/questions/3127/when-to-use-instead-of-and
>
> Signed-off-by: Oscar Utbult <oscar@oscr.io>
Acked-by: Randy Dunlap <rdunlap@infradead.org>
Jiri, for trivial, please.
> ---
> Documentation/applying-patches.txt | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/applying-patches.txt b/Documentation/applying-patches.txt
> index a083ba3..77df55b 100644
> --- a/Documentation/applying-patches.txt
> +++ b/Documentation/applying-patches.txt
> @@ -94,7 +94,7 @@ Common errors when patching
> ---
> When patch applies a patch file it attempts to verify the sanity of the
> file in different ways.
> -Checking that the file looks like a valid patch file & checking the code
> +Checking that the file looks like a valid patch file and checking the code
> around the bits being modified matches the context provided in the patch are
> just two of the basic sanity checks patch does.
>
>
--
~Randy
prev parent reply other threads:[~2014-09-25 17:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-25 13:41 [PATCH 1/1] Changed "&" with "and" in Documentation/applying-patches.txt oscar
2014-09-25 14:48 ` Frans Klaver
2014-09-25 16:28 ` Oscar Utbult
2014-09-25 19:12 ` Frans Klaver
2014-09-25 19:35 ` Randy Dunlap
2014-09-25 17:21 ` Randy Dunlap [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=54244F13.2020202@infradead.org \
--to=rdunlap@infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oscar@oscr.io \
--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