{"thread":{"id":"35135","subject":"Best practices on updating documentation?","startedAt":"2013-10-13T20:42:40Z","lastAt":"2013-10-13T21:03:04Z","messageCount":2,"participants":["brian m. carlson","John Keeping"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"228909","messageId":"20131013204240.GD865149@vauxhall.crustytoothpaste.net","threadId":"35135","inReplyTo":null,"subject":"Best practices on updating documentation?","fromName":"brian m. carlson","fromEmail":"sandals@crustytoothpaste.net","sentAt":"2013-10-13T20:42:40Z","receivedAt":"2013-10-13T20:42:40Z","isPatch":false,"sender":{"key":"sandals@crustytoothpaste.net","avatar":"https://avatars.githubusercontent.com/u/497054?v=4"},"body":"If I'm going to be adding an option to a command, should I update the\ndocumentation in the same commit or in a separate commit?\n\n-- \nbrian m. carlson / brian with sandals: Houston, Texas, US\n+1 832 623 2791 | http://www.crustytoothpaste.net/~bmc | My opinion only\nOpenPGP: RSA v4 4096b: 88AC E9B2 9196 305B A994 7552 F1BA 225C 0223 B187\n"},{"id":"228910","messageId":"20131013210304.GN27238@serenity.lan","threadId":"35135","inReplyTo":"20131013204240.GD865149@vauxhall.crustytoothpaste.net","subject":"Re: Best practices on updating documentation?","fromName":"John Keeping","fromEmail":"john@keeping.me.uk","sentAt":"2013-10-13T21:03:04Z","receivedAt":"2013-10-13T21:03:04Z","isPatch":false,"sender":{"key":"john@keeping.me.uk","avatar":"https://avatars.githubusercontent.com/u/1702081?v=4"},"body":"On Sun, Oct 13, 2013 at 08:42:40PM +0000, brian m. carlson wrote:\n> If I'm going to be adding an option to a command, should I update the\n> documentation in the same commit or in a separate commit?\n\nI would say the same commit, where it can help a reviewer see the code\nchange in the context of the expected user-facing behaviour.\n"}]}