From: "brian m. carlson" <sandals@crustytoothpaste.net>
To: Michael Kielstra <pmkielstra@college.harvard.edu>
Cc: git@vger.kernel.org
Subject: Re: Pull vs push messages
Date: Thu, 11 Jul 2019 22:01:19 +0000 [thread overview]
Message-ID: <20190711220118.GL9224@genre.crustytoothpaste.net> (raw)
In-Reply-To: <CACf0ZibKt-mpqpavmK3SVMC-Lqm9KB9kUvPj-KFkvT_LVRyOZw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1270 bytes --]
On 2019-07-11 at 21:36:50, Michael Kielstra wrote:
> Hi all,
>
> I noticed that git pull reports "Already up to date." but git push
> reports "Everything up-to-date". (I'm using git 2.20.1, the latest in
> the Ubuntu repos.) Just for a consistent user experience, would it be
> worth standardizing on:
>
> Hyphenation (up-to-date vs up to date)?
> Periods at the end of one-sentence messages?
> Colloquialisms and tone of voice? "Already up to date." sounds like a
> terse error message but "Everything up-to-date" sounds like a chatty
> friend.
>
> Maybe none of this is worth the effort, but I thought I'd mention it
> just in case.
I'd be happy to review a patch that changes this, if you think it's
worth changing. Generally the way things work here is that except for
obvious bugs, people send patches for things they care about, and then
other folks will review and make suggestions, or sometimes there won't
be any interest in a change, and the patch is dropped.
We'd probably want to standardize on "up to date", since that's the
correct form here according to the Chicago Manual of Style, and drop the
period, since this isn't a complete sentence.
--
brian m. carlson: Houston, Texas, US
OpenPGP: https://keybase.io/bk2204
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 868 bytes --]
next prev parent reply other threads:[~2019-07-11 22:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-11 21:36 Pull vs push messages Michael Kielstra
2019-07-11 22:01 ` brian m. carlson [this message]
2019-07-12 6:39 ` 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=20190711220118.GL9224@genre.crustytoothpaste.net \
--to=sandals@crustytoothpaste.net \
--cc=git@vger.kernel.org \
--cc=pmkielstra@college.harvard.edu \
/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).