* Pull vs push messages @ 2019-07-11 21:36 Michael Kielstra 2019-07-11 22:01 ` brian m. carlson 0 siblings, 1 reply; 3+ messages in thread From: Michael Kielstra @ 2019-07-11 21:36 UTC (permalink / raw) To: git 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. Michael Kielstra ^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Pull vs push messages 2019-07-11 21:36 Pull vs push messages Michael Kielstra @ 2019-07-11 22:01 ` brian m. carlson 2019-07-12 6:39 ` Martin Ågren 0 siblings, 1 reply; 3+ messages in thread From: brian m. carlson @ 2019-07-11 22:01 UTC (permalink / raw) To: Michael Kielstra; +Cc: git [-- 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 --] ^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Pull vs push messages 2019-07-11 22:01 ` brian m. carlson @ 2019-07-12 6:39 ` Martin Ågren 0 siblings, 0 replies; 3+ messages in thread From: Martin Ågren @ 2019-07-12 6:39 UTC (permalink / raw) To: brian m. carlson, Michael Kielstra, Git Mailing List On Fri, 12 Jul 2019 at 00:16, brian m. carlson <sandals@crustytoothpaste.net> wrote: > > 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. > > 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. There's 7560f547e6 ('treewide: correct several "up-to-date" to "up to date"', 2017-08-23), which changed a few of these, but also explains why it leaves "Everything up-to-date" unchanged. Whether that assessment is the One True Way now 2 years later, I'm not the right person to say. Michael, you can perhaps find some discussion leading up to / about that patch on https://public-archive.org/git/ Martin ^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2019-07-12 6:39 UTC | newest] Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2019-07-11 21:36 Pull vs push messages Michael Kielstra 2019-07-11 22:01 ` brian m. carlson 2019-07-12 6:39 ` Martin Ågren
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).