util-linux.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael Kerrisk <mtk.manpages@gmail.com>
To: Nuno Silva <nunojsilva@ist.utl.pt>
Cc: util-linux@vger.kernel.org, Karel Zak <kzak@redhat.com>,
	Michael Kerrisk-manpages <mtk.manpages@gmail.com>
Subject: Re: [PATCH 04/12] Manual pages: sfdisk.8: Minor wording and formatting fixes
Date: Thu, 27 Aug 2020 17:16:35 +0200	[thread overview]
Message-ID: <CALxWeYpTakVkzRtzMPdGvtr0T7=0u+WKQZ8AxQAZkWA7qJvWJQ@mail.gmail.com> (raw)
In-Reply-To: <rff2f1$77s$2@ciao.gmane.io>

Hi Nuno,

On Fri, Jul 24, 2020 at 6:33 PM Nuno Silva <nunojsilva@ist.utl.pt> wrote:
>
> On 2020-07-24, Michael Kerrisk (man-pages) wrote:
>
> > Signed-off-by: Michael Kerrisk (man-pages)
> > <mtk.manpages@gmail.com>
> > ---
> >  disk-utils/sfdisk.8 | 38 +++++++++++++++++++++++++++-----------
> >  1 file changed, 27 insertions(+), 11 deletions(-)
> >
> > diff --git a/disk-utils/sfdisk.8 b/disk-utils/sfdisk.8
> > index 6c3f62edd..6c54a1699 100644
> > --- a/disk-utils/sfdisk.8
> > +++ b/disk-utils/sfdisk.8
> [...]
> > @@ -601,7 +615,9 @@ The welcome message.
> >
> >  .SH ENVIRONMENT
> >  .IP SFDISK_DEBUG=all
> > -enables sfdisk debug output.
> > +enablescw
>
> And here "enables", not "enablescw"?

Yes; thanks. I've sent a patch to fix the two typos that you noticed.

Just a note though: when you strip the CC from a message, it's very
likely (because of things like individual mail filtering rules) that
relevant people will *not* notice your mail. It's best to always
preserve the CC list, unless there's some good reason not to.

Cheers,

Michael

  reply	other threads:[~2020-08-27 15:17 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-24 10:06 [PATCH 01/12] Manual pages: blockdev.8: Minor wording and formatting fixes Michael Kerrisk (man-pages)
2020-07-24 10:06 ` [PATCH 02/12] Manual pages: fsck.cramfs.8: Wording fix Michael Kerrisk (man-pages)
2020-07-24 10:06 ` [PATCH 03/12] Manual pages: raw.8: Minor formatting and wording fixes Michael Kerrisk (man-pages)
2020-07-24 10:06 ` [PATCH 04/12] Manual pages: sfdisk.8: Minor wording and formatting fixes Michael Kerrisk (man-pages)
2020-07-24 16:32   ` Nuno Silva
2020-08-27 15:16     ` Michael Kerrisk [this message]
2020-08-28 11:09       ` Nuno Silva
2020-07-24 10:06 ` [PATCH 05/12] Manual pages: sfdisk.8: Use less aggressive indenting Michael Kerrisk (man-pages)
2020-07-24 10:06 ` [PATCH 06/12] Manual pages: lslogins.1: Minor wording and formatting fixres Michael Kerrisk (man-pages)
2020-07-24 10:06 ` [PATCH 07/12] Manual pages: nologin.8: formatting fixes Michael Kerrisk (man-pages)
2020-07-24 10:06 ` [PATCH 08/12] Manual pages: logger.1: minor formatting and typo fixes Michael Kerrisk (man-pages)
2020-07-24 10:06 ` [PATCH 09/12] Manual pages: lsblk.8: Minor " Michael Kerrisk (man-pages)
2020-07-24 10:06 ` [PATCH 10/12] Manual pages: wdctl.8: typo fix Michael Kerrisk (man-pages)
2020-07-24 10:06 ` [PATCH 11/12] Manual pages: agetty.8: Minor formatting and wording fixes Michael Kerrisk (man-pages)
2020-07-24 10:06 ` [PATCH 12/12] Manual pages: wipefs.8: Formatting fixes Michael Kerrisk (man-pages)
2020-07-24 12:43 ` [PATCH 01/12] Manual pages: blockdev.8: Minor wording and formatting fixes Karel Zak
2020-07-24 16:07 ` Nuno Silva

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='CALxWeYpTakVkzRtzMPdGvtr0T7=0u+WKQZ8AxQAZkWA7qJvWJQ@mail.gmail.com' \
    --to=mtk.manpages@gmail.com \
    --cc=kzak@redhat.com \
    --cc=nunojsilva@ist.utl.pt \
    --cc=util-linux@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 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).