All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nathan Cutler <ncutler@suse.cz>
To: Ceph Development <ceph-devel@vger.kernel.org>
Subject: [PATCH] ceph-disk: s/prefered/preferred/
Date: Fri, 1 Apr 2016 08:56:17 +0200	[thread overview]
Message-ID: <56FE1B91.2080108@suse.cz> (raw)

Hi,

Please pull the following Ceph updates from this mail.

There is not much here, just some overdue proofreading.

This patch is based on a recent merge of the jewel tree to avoid 
conflicts with a recent refactor.

Sincerely

Signed-off-by: Nathan Cutler <ncutler@suse.cz>
---
  src/ceph-disk/ceph_disk/main.py | 4 ++--
  1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/src/ceph-disk/ceph_disk/main.py 
b/src/ceph-disk/ceph_disk/main.py
index d0ec596..a137967 100755
--- a/src/ceph-disk/ceph_disk/main.py
+++ b/src/ceph-disk/ceph_disk/main.py
@@ -406,7 +406,7 @@ def command(arguments, **kwargs):
      executable exists and raising a helpful error message
      if it does not.

-    .. note:: This should be the prefered way of calling 
``subprocess.Popen``
+    .. note:: This should be the preferred way of calling 
``subprocess.Popen``
      since it provides the caller with the safety net of making sure that
      executables *will* be found and will error nicely otherwise.

@@ -429,7 +429,7 @@ def command_check_call(arguments):
      Safely execute a ``subprocess.check_call`` call making sure that the
      executable exists and raising a helpful error message if it does not.

-    .. note:: This should be the prefered way of calling
+    .. note:: This should be the preferred way of calling
      ``subprocess.check_call`` since it provides the caller with the 
safety net
      of making sure that executables *will* be found and will error nicely
      otherwise.

             reply	other threads:[~2016-04-01  6:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-01  6:56 Nathan Cutler [this message]
2016-04-01  7:22 ` [PATCH] ceph-disk: s/prefered/preferred/ Dan van der Ster
2016-04-01  9:07 ` Loic Dachary
2016-04-01 10:19   ` John Hunter

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=56FE1B91.2080108@suse.cz \
    --to=ncutler@suse.cz \
    --cc=ceph-devel@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.