{"thread":{"id":"45687","subject":"\"up-to-date\" vs. \"up to date\"","startedAt":"2017-04-13T20:34:43Z","lastAt":"2017-04-15T04:34:43Z","messageCount":2,"participants":["Jeffrey Manian","brian m. carlson"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"316781","messageId":"CALFtnmeRxgetuCVbO8ZmVkCR302vQ2s4hTPoHxAe5NEfmjtXEg@mail.gmail.com","threadId":"45687","inReplyTo":null,"subject":"\"up-to-date\" vs. \"up to date\"","fromName":"Jeffrey Manian","fromEmail":"jeffrey.manian@gmail.com","sentAt":"2017-04-13T20:34:16Z","receivedAt":"2017-04-13T20:34:43Z","isPatch":false,"sender":{"key":"jeffrey.manian@gmail.com","avatar":null},"body":"Hello git community,\n\nThis is about an issue of language style and punctuation, not anything\nfunctional. Apologies in advance if I've brought this to the wrong\nplace.\n\nThere are a bunch of situations in which git will print a message like\n\"Your branch is up-to-date with 'origin/master'\" or \"Already\nup-to-date.\"\n\nIn many of these cases, including the two examples I just gave, \"up to\ndate\" should not be hyphenated --- at least according to most (if not\nall) English-language style guides.\n\nHere are a couple posts in support of that, which also explain when it\nshould and should not be hyphenated:\nhttps://english.stackexchange.com/questions/180611/do-i-keep-myself-up-to-date-or-up-to-date-on-something\nhttp://grammarist.com/usage/up-to-date/\n\nAnd the Chromium community dealing with the same issue:\nhttps://groups.google.com/a/chromium.org/forum/#!topic/chromium-reviews/edodON6G2oY\n\nI thought about submitting a patch, but I started looking through the\nsource code and found that \"up-to-date\" appears 61 times. So before I\nget into that I thought I would check with the community to see if\nthis is something that's already been debated and decided.\n\nAwaiting your thoughts,\nJeff Manian\n"},{"id":"316870","messageId":"20170415043429.ymrex77bfil2qbge@genre.crustytoothpaste.net","threadId":"45687","inReplyTo":"CALFtnmeRxgetuCVbO8ZmVkCR302vQ2s4hTPoHxAe5NEfmjtXEg@mail.gmail.com","subject":"Re: \"up-to-date\" vs. \"up to date\"","fromName":"brian m. carlson","fromEmail":"sandals@crustytoothpaste.net","sentAt":"2017-04-15T04:34:30Z","receivedAt":"2017-04-15T04:34:43Z","isPatch":false,"sender":{"key":"sandals@crustytoothpaste.net","avatar":"https://avatars.githubusercontent.com/u/497054?v=4"},"body":"On Thu, Apr 13, 2017 at 04:34:16PM -0400, Jeffrey Manian wrote:\n> Hello git community,\n> \n> This is about an issue of language style and punctuation, not anything\n> functional. Apologies in advance if I've brought this to the wrong\n> place.\n> \n> There are a bunch of situations in which git will print a message like\n> \"Your branch is up-to-date with 'origin/master'\" or \"Already\n> up-to-date.\"\n> \n> In many of these cases, including the two examples I just gave, \"up to\n> date\" should not be hyphenated --- at least according to most (if not\n> all) English-language style guides.\n\nYes, the Chicago Manual of Style agrees that \"[i]f the phrasal adjective\nfollows a verb, it is usually unhyphenated.\"  I often keep this rule in\nmind when writing commit messages.\n\n> Here are a couple posts in support of that, which also explain when it\n> should and should not be hyphenated:\n> https://english.stackexchange.com/questions/180611/do-i-keep-myself-up-to-date-or-up-to-date-on-something\n> http://grammarist.com/usage/up-to-date/\n> \n> And the Chromium community dealing with the same issue:\n> https://groups.google.com/a/chromium.org/forum/#!topic/chromium-reviews/edodON6G2oY\n> \n> I thought about submitting a patch, but I started looking through the\n> source code and found that \"up-to-date\" appears 61 times. So before I\n> get into that I thought I would check with the community to see if\n> this is something that's already been debated and decided.\n\nTo my knowledge, we haven't discussed this issue before.  I'm not Junio,\nso I can't speak for whether a patch would ultimately be accepted, but\nI'm not opposed to seeing or reviewing such a patch.\n\nGenerally, the rule on the list is that unless the change is very large\nor wide ranging, you'll find people are more likely to give you feedback\non a concrete patch (including whether the idea is desirable) than on an\nidea in general.\n-- \nbrian m. carlson / brian with sandals: Houston, Texas, US\n+1 832 623 2791 | https://www.crustytoothpaste.net/~bmc | My opinion only\nOpenPGP: https://keybase.io/bk2204\n"}]}