git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "Martin Ågren" <martin.agren@gmail.com>
Cc: STEVEN WHITE <stevencharleswhitevoices@gmail.com>,
	Git Mailing List <git@vger.kernel.org>
Subject: Re: "Your branch is up-to-date ..." is incorrect English grammar
Date: Mon, 21 Aug 2017 15:37:16 -0700	[thread overview]
Message-ID: <xmqqmv6s5yzn.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <CAN0heSrh_+J=LQnGZtngxQbcHAjFhX9vPKKDa7_ORz4iDpXf=g@mail.gmail.com> ("Martin Ågren"'s message of "Mon, 21 Aug 2017 11:37:39 +0200")

Martin Ågren <martin.agren@gmail.com> writes:

>> But “your branch is up-to-date” is INCORRECT. And, because it’s
>> incorrect, it conveys an odd and unsettling experience to native
>> English speakers whenever they read it.
>>
>> If you’re curious, you can find plenty of discussion of this point of
>> grammar. Here’s just one example:
>> https://english.stackexchange.com/questions/180611/do-i-keep-myself-up-to-date-or-up-to-date-on-something.
>
> There is also some previous discussion on this very list:
> https://public-inbox.org/git/CALFtnmeRxgetuCVbO8ZmVkCR302vQ2s4hTPoHxAe5NEfmjtXEg@mail.gmail.com/T/#u
>
> The code base contains a few instances of "up-to-date" and "up to date".
> A tree wide sweep could be made to update user-visible strings in the
> code and in the documentation. Fixing source code comments seems like
> overkill.

It should be safe to update any message that is meant for human
consumption (i.e. those inside the _("... message ...")) i18n
marker).  As the use of "up-to-date" dates back to the days when
Linus was still doing much code for our project, I suspect there may
be some plumbing message that contains the phrase that scripts
expect to stay spelled that way, and it is not OK to "fix" them.

Thanks.

  reply	other threads:[~2017-08-21 22:37 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-21  8:21 "Your branch is up-to-date ..." is incorrect English grammar STEVEN WHITE
2017-08-21  9:37 ` Martin Ågren
2017-08-21 22:37   ` Junio C Hamano [this message]
2017-08-23  3:55     ` STEVEN WHITE
2017-08-23 17:49       ` [PATCH 1/2] Documentation/user-manual: update outdated example output Martin Ågren
2017-08-23 19:02         ` Junio C Hamano
2017-08-23 17:49       ` [PATCH 2/2] treewide: correct several "up-to-date" to "up to date" Martin Ågren
2017-08-24  3:51         ` STEVEN WHITE
2017-08-24  9:48           ` Martin Ågren

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=xmqqmv6s5yzn.fsf@gitster.mtv.corp.google.com \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=martin.agren@gmail.com \
    --cc=stevencharleswhitevoices@gmail.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).