{"thread":{"id":"33750","subject":"Minor correction to Git book","startedAt":"2013-05-08T10:24:56Z","lastAt":"2013-05-08T11:08:44Z","messageCount":4,"participants":["Robin Messer","John Keeping"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"216692","messageId":"71E08C07CB3C444098033ABD69925159145BB1DDE1@BATH-EXCMS.praxis.local","threadId":"33750","inReplyTo":null,"subject":"Minor correction to Git book","fromName":"Robin Messer","fromEmail":"robin.messer@altran.com","sentAt":"2013-05-08T10:24:56Z","receivedAt":"2013-05-08T10:24:56Z","isPatch":false,"sender":{"key":"robin.messer@altran.com","avatar":null},"body":"I'm just learning Git so I don't yet know how to submit this\nas a patch, but I'm reading the Git Book to get myself started\nand I think there is a mistake on the page at:\n\nhttp://git-scm.com/book/en/Git-Basics-Recording-Changes-to-the-Repository\n\nIt says: \"For another example, if you stage the benchmarks.rb file and\nthen edit it, you can use git diff to see the changes in the file that\nare staged and the changes that are unstaged:\"\n\nI believe this should say \"git status\" rather than \"git diff\".\n\n--\nRobin\n\nThis email is confidential and intended solely for the use of the individual to whom it is addressed. If you are not the intended recipient, be advised that you have received this email in error and that any use, disclosure, copying or distribution or any action taken or omitted to be taken in reliance on it is strictly prohibited. If you have received this email in error please contact the sender. Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of Altran.\n\nAlthough this email and any attachments are believed to be free of any virus or other defect, no responsibility is accepted by Altran or any of its associated companies for any loss or damage arising in any way from the receipt or use thereof.\n\nAltran UK Ltd:\n\nCompany Number: 3302507, registered in England and Wales\n\nRegistered Address: 22 St. Lawrence Street, Bath, BA1 1AN\n\nVAT Registered in Great Britain: 682635707\n"},{"id":"216694","messageId":"20130508105141.GH25912@serenity.lan","threadId":"33750","inReplyTo":"71E08C07CB3C444098033ABD69925159145BB1DDE1@BATH-EXCMS.praxis.local","subject":"Re: Minor correction to Git book","fromName":"John Keeping","fromEmail":"john@keeping.me.uk","sentAt":"2013-05-08T10:51:42Z","receivedAt":"2013-05-08T10:51:42Z","isPatch":false,"sender":{"key":"john@keeping.me.uk","avatar":"https://avatars.githubusercontent.com/u/1702081?v=4"},"body":"On Wed, May 08, 2013 at 11:24:56AM +0100, Robin Messer wrote:\n> I'm just learning Git so I don't yet know how to submit this\n> as a patch, but I'm reading the Git Book to get myself started\n> and I think there is a mistake on the page at:\n> \n> http://git-scm.com/book/en/Git-Basics-Recording-Changes-to-the-Repository\n> \n> It says: \"For another example, if you stage the benchmarks.rb file and\n> then edit it, you can use git diff to see the changes in the file that\n> are staged and the changes that are unstaged:\"\n> \n> I believe this should say \"git status\" rather than \"git diff\".\n\nI think the text is correct as it stands.  \"git status\" shows you that\nthere are changes that are staged and unstaged, \"git diff\" (and \"git\ndiff --cached\") shows you what those changes are.\n"},{"id":"216695","messageId":"71E08C07CB3C444098033ABD69925159145BB1DE33@BATH-EXCMS.praxis.local","threadId":"33750","inReplyTo":"20130508105141.GH25912@serenity.lan","subject":"RE: Minor correction to Git book","fromName":"Robin Messer","fromEmail":"robin.messer@altran.com","sentAt":"2013-05-08T11:01:00Z","receivedAt":"2013-05-08T11:01:00Z","isPatch":false,"sender":{"key":"robin.messer@altran.com","avatar":null},"body":"> I think the text is correct as it stands.  \"git status\" shows you that\n> there are changes that are staged and unstaged, \"git diff\" (and \"git\n> diff --cached\") shows you what those changes are.\n\nThanks, but the command line which follows that text does actually use\n\"git status\" to show which files (staged and unstaged) have changes.\nThe text I quoted is introducing that command.\n\nThen the next example shows you how to use \"git diff\" to see what the\nactual unstaged changes to those files are.\n\nIf this is not the appropriate place to report such things, please point\nme at the correct one.\n\nThanks,\n\nRobin.\n\nThis email is confidential and intended solely for the use of the individual to whom it is addressed. If you are not the intended recipient, be advised that you have received this email in error and that any use, disclosure, copying or distribution or any action taken or omitted to be taken in reliance on it is strictly prohibited. If you have received this email in error please contact the sender. Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of Altran.\n\nAlthough this email and any attachments are believed to be free of any virus or other defect, no responsibility is accepted by Altran or any of its associated companies for any loss or damage arising in any way from the receipt or use thereof.\n\nAltran UK Ltd:\n\nCompany Number: 3302507, registered in England and Wales\n\nRegistered Address: 22 St. Lawrence Street, Bath, BA1 1AN\n\nVAT Registered in Great Britain: 682635707\n"},{"id":"216696","messageId":"20130508110844.GI25912@serenity.lan","threadId":"33750","inReplyTo":"71E08C07CB3C444098033ABD69925159145BB1DE33@BATH-EXCMS.praxis.local","subject":"Re: Minor correction to Git book","fromName":"John Keeping","fromEmail":"john@keeping.me.uk","sentAt":"2013-05-08T11:08:44Z","receivedAt":"2013-05-08T11:08:44Z","isPatch":false,"sender":{"key":"john@keeping.me.uk","avatar":"https://avatars.githubusercontent.com/u/1702081?v=4"},"body":"On Wed, May 08, 2013 at 12:01:00PM +0100, Robin Messer wrote:\n> > I think the text is correct as it stands.  \"git status\" shows you that\n> > there are changes that are staged and unstaged, \"git diff\" (and \"git\n> > diff --cached\") shows you what those changes are.\n> \n> Thanks, but the command line which follows that text does actually use\n> \"git status\" to show which files (staged and unstaged) have changes.\n> The text I quoted is introducing that command.\n> \n> Then the next example shows you how to use \"git diff\" to see what the\n> actual unstaged changes to those files are.\n\nAh, OK.  I read your email without looking at the context.\n\n> If this is not the appropriate place to report such things, please point\n> me at the correct one.\n\nThe ProGit book is maintained at https://github.com/progit/progit\n"}]}