From: Oscar Utbult <oscar@oscr.io>
To: Frans Klaver <fransklaver@gmail.com>
Cc: Randy Dunlap <rdunlap@infradead.org>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] Changed "&" with "and" in Documentation/applying-patches.txt.
Date: Thu, 25 Sep 2014 18:28:47 +0200 [thread overview]
Message-ID: <e692e73445c591af1bea3ce0a87755c6@oscr.io> (raw)
In-Reply-To: <CAH6sp9NqiNincavwB9bQ94EvG8ZjvUPLH5u3j04OV2JMz7wTEg@mail.gmail.com>
On 2014-09-25 16:48, Frans Klaver wrote:
> On Thu, Sep 25, 2014 at 3:41 PM, <oscar@oscr.io> wrote:
>> Subject: [PATCH 1/1] Changed "&" with "and" in
>> Documentation/applying-patches.txt.
>
> Documentation/SubmittingPatches says:
>
> Describe your changes in imperative mood, e.g. "make xyzzy do frotz"
> instead of "[This patch] makes xyzzy do frotz" or "[I] changed xyzzy
> to do frotz", as if you are giving orders to the codebase to change
> its behaviour.
Thank you for your feedback Frans.
So for example a better description would have been: "use 'and' instead
of '&'"?
>
>> From: Oscar Utbult <oscar@oscr.io>
>>
>> http://english.stackexchange.com/questions/3127/when-to-use-instead-of-and
>
> It might be that a link is enough, but I would prefer to have an
> excerpt from that, possibly with the link as reference.
You are right. I will provide one in the future.
Oscar
>
> Thanks,
> Frans
>
>>
>> Signed-off-by: Oscar Utbult <oscar@oscr.io>
>> ---
>> 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.
>>
>> --
>> 1.8.0.1
>>
>> --
>> To unsubscribe from this list: send the line "unsubscribe
>> linux-kernel" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>> Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2014-09-25 16:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-25 13:41 oscar
2014-09-25 14:48 ` Frans Klaver
2014-09-25 16:28 ` Oscar Utbult [this message]
2014-09-25 19:12 ` Frans Klaver
2014-09-25 19:35 ` Randy Dunlap
2014-09-25 17:21 ` Randy Dunlap
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=e692e73445c591af1bea3ce0a87755c6@oscr.io \
--to=oscar@oscr.io \
--cc=fransklaver@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.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
Powered by JetHome