qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Stefan Hajnoczi <stefanha@redhat.com>
Cc: mst@redhat.com, jag.raman@oracle.com, qemu-devel@nongnu.org,
	sgarzare@redhat.com
Subject: Re: [PATCH 3/3] docs: vhost-user: replace master/slave with front-end/back-end
Date: Mon, 1 Mar 2021 11:48:42 +0100	[thread overview]
Message-ID: <77fda1e7-c26b-3c45-d840-0600b4455d01@redhat.com> (raw)
In-Reply-To: <YDzArmIIkO1GHoIz@stefanha-x1.localdomain>

On 01/03/21 11:23, Stefan Hajnoczi wrote:
> The spec uses "backend" but this patch uses "back-end".
> 
> Searching the web shows that "back end", "back-end", and "backend" are
> all commonly used. I don't think there is a right or wrong choice since
> all spellings are popular. It would be nice to stay consistent and use
> "backend"/"frontend" in this document.

Ok, will fix in v2.

Paolo



  reply	other threads:[~2021-03-01 10:49 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-26 14:34 [PATCH 0/3] docs: replace master/slave with more accurate wording Paolo Bonzini
2021-02-26 14:34 ` [PATCH 1/3] docs: vhost-user: clean up request/reply description Paolo Bonzini
2021-03-01  8:12   ` Philippe Mathieu-Daudé
2021-03-01 10:16   ` Stefan Hajnoczi
2021-03-01 10:32   ` Stefano Garzarella
2021-03-01 10:49     ` Paolo Bonzini
2021-03-01 11:33   ` Alex Bennée
2021-02-26 14:34 ` [PATCH 2/3] docs: vhost-user: rewrite section on ring state machine Paolo Bonzini
2021-03-01 10:16   ` Stefan Hajnoczi
2021-02-26 14:34 ` [PATCH 3/3] docs: vhost-user: replace master/slave with front-end/back-end Paolo Bonzini
2021-03-01 10:23   ` Stefan Hajnoczi
2021-03-01 10:48     ` Paolo Bonzini [this message]
2021-02-26 14:48 ` [PATCH 0/3] docs: replace master/slave with more accurate wording Jag Raman

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=77fda1e7-c26b-3c45-d840-0600b4455d01@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=jag.raman@oracle.com \
    --cc=mst@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=sgarzare@redhat.com \
    --cc=stefanha@redhat.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;
as well as URLs for NNTP newsgroup(s).