git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Michael J Gruber <git@drmicha.warpmail.net>
To: Felipe Contreras <felipe.contreras@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: [PATCH 3/3] user-manual: use 'fast-forward'
Date: Mon, 12 Oct 2009 14:50:07 +0200	[thread overview]
Message-ID: <4AD325FF.6070105@drmicha.warpmail.net> (raw)
In-Reply-To: <94a0d4530910120305o49ed7c74sf6a03097b1098a5f@mail.gmail.com>

Felipe Contreras venit, vidit, dixit 12.10.2009 12:05:
> On Mon, Oct 12, 2009 at 8:05 AM, Junio C Hamano <gitster@pobox.com> wrote:
>> Felipe Contreras <felipe.contreras@gmail.com> writes:
>>
>>> It's a compound word.
>>
>> Thanks.
>>
>> This removes 7 out of 37 "fast forward" in Documentation/ directory.  Are
>> we going to convert the remaining ones, too?
> 
> Sure. Once I finish pushing the patches I have for user-manual, which
> is the one I'm interested right now.
> 

And how about the other 40 or so in the remaining code?

In fact, hyphenated and separated forms of this compound noun are almost
evenly split, which reflects well upon the fact that there is no
clear-cut rule in US English (and neither in BE).

So, if you are suggesting a style we should define it and follow it
consistently. Our main source of definitions is the glossary. Now, that
has a truly salomonic solution:

fast forward
	A fast-forward is a special type...

I suggest that this is the first place which needs attention, after
fixating the definition, maybe not just among the three of us, all
non-native speakers.

Michael

  reply	other threads:[~2009-10-12 12:57 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-11 20:46 [PATCH 0/3] Trivial patches Felipe Contreras
2009-10-11 20:46 ` [PATCH 1/3] Fix a bunch of pointer declarations (codestyle) Felipe Contreras
2009-10-11 20:46   ` [PATCH 2/3] git config: clarify bool types Felipe Contreras
2009-10-11 20:46     ` [PATCH 3/3] user-manual: use 'fast-forward' Felipe Contreras
2009-10-12  5:05       ` Junio C Hamano
2009-10-12 10:05         ` Felipe Contreras
2009-10-12 12:50           ` Michael J Gruber [this message]
2009-10-12  5:01     ` [PATCH 2/3] git config: clarify bool types Junio C Hamano
2009-10-12 10:03       ` Felipe Contreras
2009-10-12 12:30         ` Michael J Gruber
2009-10-12 17:14           ` Felipe Contreras
2009-10-13  7:09             ` Michael J Gruber
2009-10-13 10:02               ` Felipe Contreras
2009-10-11 20:53   ` [PATCH 1/3] Fix a bunch of pointer declarations (codestyle) Thiago Farina
2009-10-11 20:56     ` Felipe Contreras

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=4AD325FF.6070105@drmicha.warpmail.net \
    --to=git@drmicha.warpmail.net \
    --cc=felipe.contreras@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.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).