From: Junio C Hamano <gitster@pobox.com>
To: Marc Branchaud <marcnarc@xiplink.com>
Cc: git@vger.kernel.org, Fredrik Gustafsson <iveqy@iveqy.com>
Subject: Re: [PATCH v2] Provide some linguistic guidance for the documentation.
Date: Thu, 01 Aug 2013 11:21:06 -0700 [thread overview]
Message-ID: <7vfvuts25p.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <1375369825-28636-1-git-send-email-marcnarc@xiplink.com> (Marc Branchaud's message of "Thu, 1 Aug 2013 11:10:25 -0400")
Marc Branchaud <marcnarc@xiplink.com> writes:
> + The documentation generally follows US English (en_US) norms for spelling
> + and grammar, although most spelling variations are tolerated. Just avoid
> + mixing styles when updating existing text. If you wish to correct the
> + English of some of the existing documentation, please see the documentation-
> + related advice in the Documentation/SubmittingPatches file.
Is that accurate? My impression has been:
The documentation liberally mixes US and UK English (en_US/UK)
norms for spelling and grammar, which is somewhat unfortunate.
In an ideal world, it would have been better if it consistently
used only one and not the other, and we would have picked en_US.
A huge patch that touches the files all over the place only to
correct the inconsistency is not welcome, though. Potential
clashes with other changes that can result from such a patch is
simply not worth it. What we would want is to gradually convert
them, with small and easily digestable patches, as a side effect
of doing some other _real_ work in the vicinity (e.g. rewriting
a paragraph to clarify, while turning en_UK spelling to en_US).
next prev parent reply other threads:[~2013-08-01 18:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-29 21:15 [PATCH] Documentation: fix typos in man pages Øystein Walle
2013-07-30 14:51 ` Marc Branchaud
2013-07-30 15:05 ` Junio C Hamano
2013-07-30 15:11 ` [PATCH] Specify UK English for the documentation source files Marc Branchaud
2013-07-30 15:52 ` Fredrik Gustafsson
2013-07-30 16:40 ` Junio C Hamano
2013-08-01 15:10 ` [PATCH v2] Provide some linguistic guidance for the documentation Marc Branchaud
2013-08-01 15:14 ` Marc Branchaud
2013-08-01 18:21 ` Junio C Hamano [this message]
2013-08-01 18:49 ` [PATCH v3] " Marc Branchaud
2013-08-02 6:25 ` [PATCH v2] " Jonathan Nieder
2013-08-02 14:16 ` Marc Branchaud
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7vfvuts25p.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=iveqy@iveqy.com \
--cc=marcnarc@xiplink.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).