{"thread":{"id":"46188","subject":"[BUG] GITK don't show unstaged changes","startedAt":"2017-06-15T11:52:52Z","lastAt":"2017-06-16T12:18:04Z","messageCount":3,"participants":["Clébio C. Felix","Konstantin Khomoutov"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"322315","messageId":"1527808373.12987632.1497527566906@mail.yahoo.com","threadId":"46188","inReplyTo":"905919609.12947564.1497527369339@mail.yahoo.com","subject":"[BUG] GITK don't show unstaged changes","fromName":"Clébio C. Felix","fromEmail":"clebiofelix@yahoo.com.br","sentAt":"2017-06-15T11:52:46Z","receivedAt":"2017-06-15T11:52:52Z","isPatch":false,"sender":{"key":"clebiofelix@yahoo.com.br","avatar":null},"body":"\nDetails:  https://github.com/git-for-windows/git/issues/1203  \n\nVersion with bug: 2.13.1\nNormal: 2.13.0\n\n\nCCFelix\n"},{"id":"322450","messageId":"1466340834.14042132.1497612459300@mail.yahoo.com","threadId":"46188","inReplyTo":"20170616063031.mxx72dlg5ccc3vtq@tigra","subject":"Re: [BUG] GITK don't show unstaged changes","fromName":"Clébio C. Felix","fromEmail":"clebiofelix@yahoo.com.br","sentAt":"2017-06-16T11:27:39Z","receivedAt":"2017-06-16T11:34:57Z","isPatch":false,"sender":{"key":"clebiofelix@yahoo.com.br","avatar":null},"body":"If this is an intentional change and not a bug, then gitk has become less useful to me, since I've always used it to do a quick review before committing. It's easier than using bash. Sad.\n\n\n:-(\n\n________________________________\nDe: Konstantin Khomoutov <kostix+git@007spb.ru>\nPara: Clébio C. Felix <clebiofelix@yahoo.com.br> \nCc: git@vger.kernel.org\nEnviadas: Sexta-feira, 16 de Junho de 2017 3:30\nAssunto: Re: [BUG] GITK don't show unstaged changes\n\n\nOn Thu, Jun 15, 2017 at 11:52:46AM +0000, Clébio C. Felix wrote:\n\n\n> Details:  https://github.com/git-for-windows/git/issues/1203 \n> \n> Version with bug: 2.13.1\n> Normal: 2.13.0\n\nAttached are the pictures for those who doesn't want to browse that bug\nand dig them up.\n\nBasically, the idea is that Gitk in 2.13.1 won't show that \"Local\nuncommitted changes blah blah ...\" entry above the one representing the\ntip commit even though the `git status` command shows them.\n"},{"id":"322455","messageId":"20170616120957.finyyp2mrvtc7xf2@tigra","threadId":"46188","inReplyTo":"1466340834.14042132.1497612459300@mail.yahoo.com","subject":"Re: [BUG] GITK don't show unstaged changes","fromName":"Konstantin Khomoutov","fromEmail":"flatworm@users.sourceforge.net","sentAt":"2017-06-16T12:09:57Z","receivedAt":"2017-06-16T12:18:04Z","isPatch":false,"sender":{"key":"flatworm@users.sourceforge.net","avatar":null},"body":"On Fri, Jun 16, 2017 at 11:27:39AM +0000, Clébio C. Felix wrote:\n\n>>> Details:  https://github.com/git-for-windows/git/issues/1203 \n>>> \n>>> Version with bug: 2.13.1\n>>> Normal: 2.13.0\n>> \n>> Attached are the pictures for those who doesn't want to browse that bug\n>> and dig them up.\n>> \n>> Basically, the idea is that Gitk in 2.13.1 won't show that \"Local\n>> uncommitted changes blah blah ...\" entry above the one representing the\n>> tip commit even though the `git status` command shows them.\n> If this is an intentional change and not a bug, then gitk has become\n> less useful to me, since I've always used it to do a quick review\n> before committing. It's easier than using bash. Sad.\n\nHi!\n\nWell, my message with your pic displaying the bug seemingly failed to\ncome through the filters of the list hosting software.\n\nBut while we're on it -- please, when you're asked to report your\nproblem somewhere else don't just drop a link to a prior discussion:\nchances are very high, most of those who would otherwise pay attention\nto your problem will simply skim over and ignore it whatsoever.\n\nI tried to correct this without much fuss but it seems like that did not\nquite work out ;-)\n\n"}]}