From: "Jürgen Groß" <jgross@suse.com>
To: Lars Kurth <lars.kurth@citrix.com>,
Lars Kurth <lars.kurth@xenproject.org>,
"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>
Cc: "minios-devel@lists.xenproject.org"
<minios-devel@lists.xenproject.org>,
"xen-api@lists.xenproject.org" <xen-api@lists.xenproject.org>,
"win-pv-devel@lists.xenproject.org"
<win-pv-devel@lists.xenproject.org>,
"committers@xenproject.org" <committers@xenproject.org>,
"mirageos-devel@lists.xenproject.org"
<mirageos-devel@lists.xenproject.org>
Subject: Re: [Xen-devel] [PATCH v4 7/7] Added Resolving Disagreement
Date: Mon, 6 Jan 2020 14:00:58 +0100 [thread overview]
Message-ID: <a44c7bac-0e85-46b9-4db9-35ca7a803c99@suse.com> (raw)
In-Reply-To: <3993E270-A44B-4131-9BD9-E3E58C51D8D3@citrix.com>
On 06.01.20 13:54, Lars Kurth wrote:
>
>
> On 06/01/2020, 07:25, "Jürgen Groß" <jgross@suse.com> wrote:
>
> >+## Issue: Small functional issues
> >+
> >+The most common area of disagreements which happen in code reviews, are
> >+differing opinions on whether small functional issues in a patch series have to
> >+be resolved or not before the code is ready to be submitted. Such disagreements
> >+are typically caused by different expectations related to the level of
> >+perfection a patch series needs to fulfil before it can be considered ready to
>
> s/fulfil/fulfill/
>
> >+be committed.
> >+
> >+To explain this better, I am going to use the analogy of some building work that
> >+has been performed at your house. Let's say that you have a new bathroom
> >+installed. Before paying your builder the last instalment, you perform an
>
> s/instalment/installment/
>
> Hi Juergen: thank you for pointing out the remaining typos.
>
> I fixed these in my local tree, with the exception of the two instances above.
>
> The two issues above come down to US vs non-US English
>
> https://grammarist.com/spelling/fulfil-fulfill/
> https://grammarist.com/spelling/installment-instalment/
>
> I didn't really review the document for consistency with respect to a particular style of English spelling.
> It does seem though that normally I use US spelling (e.g. minimize) mostly and of course the Contributor
> Covenant has been written US spelling.
>
> I don't have a strong view either way and can have a go at making it consistent (e.g. in US stylespelling)
I'm not really feeling strong here, but I think consistency
should be the preferred way to go.
Juergen
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
prev parent reply other threads:[~2020-01-06 13:01 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-30 19:32 [Xen-devel] [PATCH v4 0/7] Code of Conduct + Extra Guides and Best Practices + VOTE Lars Kurth
2019-12-30 19:32 ` [Xen-devel] [PATCH v4 1/7] Import v1.4 of Contributor Covenant CoC Lars Kurth
2019-12-30 19:32 ` [Xen-devel] [PATCH v4 2/7] Xen Project Code of Conduct Lars Kurth
2019-12-30 19:32 ` [Xen-devel] [PATCH v4 3/7] Reformat Xen Project CoC to fit into 80 character limit Lars Kurth
2019-12-30 19:32 ` [Xen-devel] [PATCH v4 4/7] Add Communication Guide Lars Kurth
2020-01-06 6:41 ` Jürgen Groß
2019-12-30 19:32 ` [Xen-devel] [PATCH v4 5/7] Add Code Review Guide Lars Kurth
2020-01-06 7:03 ` Jürgen Groß
2019-12-30 19:32 ` [Xen-devel] [PATCH v4 6/7] Add guide on Communication Best Practice Lars Kurth
2020-01-06 7:20 ` Jürgen Groß
2020-01-13 19:54 ` George Dunlap
2020-01-13 21:21 ` Lars Kurth
2020-01-15 10:47 ` George Dunlap
2020-01-15 12:22 ` Lars Kurth
2020-01-15 17:07 ` George Dunlap
2019-12-30 19:32 ` [Xen-devel] [PATCH v4 7/7] Added Resolving Disagreement Lars Kurth
2020-01-06 7:25 ` Jürgen Groß
2020-01-06 12:54 ` Lars Kurth
2020-01-06 13:00 ` Jürgen Groß [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=a44c7bac-0e85-46b9-4db9-35ca7a803c99@suse.com \
--to=jgross@suse.com \
--cc=committers@xenproject.org \
--cc=lars.kurth@citrix.com \
--cc=lars.kurth@xenproject.org \
--cc=minios-devel@lists.xenproject.org \
--cc=mirageos-devel@lists.xenproject.org \
--cc=win-pv-devel@lists.xenproject.org \
--cc=xen-api@lists.xenproject.org \
--cc=xen-devel@lists.xenproject.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;
as well as URLs for NNTP newsgroup(s).