From: Peter Cordes <peter@cordes.ca>
To: Bill Pemberton <wfp5p@worldbroken.com>
Cc: Util-Linux <util-linux@vger.kernel.org>
Subject: Re: [PATCH 0/8] fix spelling/typos in man pages
Date: Tue, 24 Feb 2015 22:49:33 -0400 [thread overview]
Message-ID: <20150225024933.GT3933@cordes.ca> (raw)
In-Reply-To: <54ECFEC0.3050702@worldbroken.com>
On Tue, Feb 24, 2015 at 05:44:16PM -0500, Bill Pemberton wrote:
> Ok, I'm used to 1 patch 1 fix. While they're all spelling/typos they're
> not the same word/typo.
That makes sense for code, esp. to make regressions bisectable. It
just bloats the revision history for docs. Single-word fixes, even
scattered across multiple files, would be easier to look at as one
commit in the git log.
--
#define X(x,y) x##y
Peter Cordes ; e-mail: X(peter@cor , des.ca)
"The gods confound the man who first found out how to distinguish the hours!
Confound him, too, who in this place set up a sundial, to cut and hack
my day so wretchedly into small pieces!" -- Plautus, 200 BC
prev parent reply other threads:[~2015-02-25 2:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-24 17:15 [PATCH 0/8] fix spelling/typos in man pages wfp5p
2015-02-24 17:15 ` [PATCH 1/8] runuser.1: fix spelling implemenation -> implementation wfp5p
2015-02-24 17:15 ` [PATCH 2/8] scriptreplay.1: fix spelling overide -> override wfp5p
2015-02-24 17:15 ` [PATCH 3/8] unshare.1: fix spelling permamently -> permanently wfp5p
2015-02-24 17:15 ` [PATCH 4/8] last.1: fix spelling preferrable -> preferable wfp5p
2015-02-24 17:15 ` [PATCH 5/8] lslogins.1: fix spelling priviliges -> privileges wfp5p
2015-02-24 17:15 ` [PATCH 6/8] hwclock.8.in: fix spelling transfered -> transferred wfp5p
2015-02-24 17:15 ` [PATCH 7/8] prlimit.1: fix typo umlimited -> unlimited wfp5p
2015-02-24 17:15 ` [PATCH 8/8] agetty.8: fix typo unnsupported -> unsupported wfp5p
2015-02-24 21:13 ` [PATCH 0/8] fix spelling/typos in man pages Benno Schulenberg
2015-02-24 22:44 ` Bill Pemberton
2015-02-25 2:49 ` Peter Cordes [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=20150225024933.GT3933@cordes.ca \
--to=peter@cordes.ca \
--cc=util-linux@vger.kernel.org \
--cc=wfp5p@worldbroken.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