# Pull vs push messages 3 messages from 2019-07-11 to 2019-07-12. Participants: Michael Kielstra, brian m. carlson, Martin Ågren. Thread: https://gitlist.dev/t/51470 ## Michael Kielstra, 2019-07-11 21:36 Subject: Pull vs push messages Message-ID: URL: https://gitlist.dev/e/CACf0ZibKt-mpqpavmK3SVMC-Lqm9KB9kUvPj-KFkvT_LVRyOZw%40mail.gmail.com ``` 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 ``` ## brian m. carlson, 2019-07-11 22:01 Subject: Re: Pull vs push messages Message-ID: <20190711220118.GL9224@genre.crustytoothpaste.net> URL: https://gitlist.dev/e/20190711220118.GL9224%40genre.crustytoothpaste.net In-Reply-To: ``` 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 ``` ## Martin Ågren, 2019-07-12 06:39 Subject: Re: Pull vs push messages Message-ID: URL: https://gitlist.dev/e/CAN0heSp9ZsEkxNReV8EMpNzTWJCLqL2hjQir%2BoA8bkEE6zv5uA%40mail.gmail.com In-Reply-To: <20190711220118.GL9224@genre.crustytoothpaste.net> ``` On Fri, 12 Jul 2019 at 00:16, brian m. carlson 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 ```