{"thread":{"id":"44864","subject":"problem with insider build for windows and git","startedAt":"2017-01-12T16:21:50Z","lastAt":"2017-01-19T20:37:01Z","messageCount":6,"participants":["Michael Gooch","Johannes Schindelin","Junio C Hamano"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"309273","messageId":"1bddbd50-86ea-6c38-6ab8-08336de2ba72@gmail.com","threadId":"44864","inReplyTo":null,"subject":"problem with insider build for windows and git","fromName":"Michael Gooch","fromEmail":"goochmi@gmail.com","sentAt":"2017-01-12T16:21:42Z","receivedAt":"2017-01-12T16:21:50Z","isPatch":false,"sender":{"key":"goochmi@gmail.com","avatar":null},"body":"when running commands like pull and clone I get the following message:\n\nCygwin WARNING:\n Couldn't compute FAST_CWD pointer. This typically occurs if you're using\n an older Cygwin version on a newer Windows. Please update to the latest\n available Cygwin version from https://cygwin.com/. If the problem \npersists,\n please see https://cygwin.com/problems.html\n\nWindows build is version 1607, OS BUILD 15002.1001\n\nI assume they broke something that cygwin was depending on.\n\n"},{"id":"309426","messageId":"alpine.DEB.2.20.1701131300390.3469@virtualbox","threadId":"44864","inReplyTo":"1bddbd50-86ea-6c38-6ab8-08336de2ba72@gmail.com","subject":"Re: problem with insider build for windows and git","fromName":"Johannes Schindelin","fromEmail":"johannes.schindelin@gmx.de","sentAt":"2017-01-14T18:09:49Z","receivedAt":"2017-01-14T18:09:57Z","isPatch":false,"sender":{"key":"johannes.schindelin@gmx.de","avatar":"https://avatars.githubusercontent.com/u/127790?v=4"},"body":"Hi Michael,\n\nOn Thu, 12 Jan 2017, Michael Gooch wrote:\n\n> when running commands like pull and clone I get the following message:\n> \n> Cygwin WARNING:\n> Couldn't compute FAST_CWD pointer. This typically occurs if you're using\n> an older Cygwin version on a newer Windows. Please update to the latest\n> available Cygwin version from https://cygwin.com/. If the problem \n> persists,\n> please see https://cygwin.com/problems.html\n> \n> Windows build is version 1607, OS BUILD 15002.1001\n> \n> I assume they broke something that cygwin was depending on.\n\nThis is not only a known problem, we already have a fix for it, too.\n\nPlease note that the recommended way [*1*] to report bugs in Git for\nWindows would have led you to this ticket:\n\n\thttps://github.com/git-for-windows/git/issues/1029\n\nPlease also note that this is only a warning, not an error. Even so, the\nproblem has been reported independently several times...\n\nThere have been enough real fixes have been accumulated in Git for\nWindows' `master` branch, and the next official Git version is far enough\nin the future [*2*] that it was time for a Git for Windows version,\nincluding the fix for the FAST_CWD warning.\n\nCiao,\nJohannes\n\nFootnote *1*: https://git-for-windows.github.io/#contribute\n\nFootnote *2*: http://tinyurl.com/gitCal suggests that Git v2.12.0 will be\nreleased early February soon after Git Merge (and Git for Windows v2.12.0\nwill follow soon thereafter), and with no patches applied to the `maint`\nbranch since v2.11.0, I do actually not expect any v2.11.1 to happen\nbefore v2.12.0 comes out.\n"},{"id":"309632","messageId":"alpine.DEB.2.20.1701181738490.3469@virtualbox","threadId":"44864","inReplyTo":"alpine.DEB.2.20.1701131300390.3469@virtualbox","subject":"Re: problem with insider build for windows and git","fromName":"Johannes Schindelin","fromEmail":"johannes.schindelin@gmx.de","sentAt":"2017-01-18T16:41:42Z","receivedAt":"2017-01-18T16:41:52Z","isPatch":false,"sender":{"key":"johannes.schindelin@gmx.de","avatar":"https://avatars.githubusercontent.com/u/127790?v=4"},"body":"Hi,\n\nOn Sat, 14 Jan 2017, Johannes Schindelin wrote:\n\n> Footnote *2*: http://tinyurl.com/gitCal suggests that Git v2.12.0 will\n> be released early February soon after Git Merge (and Git for Windows\n> v2.12.0 will follow soon thereafter), and with no patches applied to the\n> `maint` branch since v2.11.0, I do actually not expect any v2.11.1 to\n> happen before v2.12.0 comes out.\n\nAnd just to prove me wrong, today I got the first update to `maint` in six\nweeks, with a message \"Almost ready for 2.11.1\" at its tip, featuring a\nwhopping 141 commits (95 of which are not merge commits).\n\nSo it seems that v2.11.1 may happen soon, after all.\n\nSorry for my misjudgement,\nJohannes\n"},{"id":"309635","messageId":"xmqq8tq8b4mr.fsf@gitster.mtv.corp.google.com","threadId":"44864","inReplyTo":"alpine.DEB.2.20.1701181738490.3469@virtualbox","subject":"Re: problem with insider build for windows and git","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2017-01-18T18:32:44Z","receivedAt":"2017-01-18T18:37:02Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Johannes Schindelin writes:\n\n> And just to prove me wrong, today I got the first update to `maint` in six\n> weeks, with a message \"Almost ready for 2.11.1\" at its tip, featuring a\n> whopping 141 commits (95 of which are not merge commits).\n>\n> So it seems that v2.11.1 may happen soon, after all.\n\nSorry for being late. I had a short travel around the year boundary,\ngot sick and have been slow.\n\nAside from the \"ouch, one topic has merged earlier iteration, that\nwas merged to 'master', also now merged to 'maint', and we need to\nfollow up on both\" you sent out earlier, are there any other topic\nthat are already in 'master' that should go to 2.11.x track?\n\nThanks.\n"},{"id":"309764","messageId":"alpine.DEB.2.20.1701192032330.3469@virtualbox","threadId":"44864","inReplyTo":"xmqq8tq8b4mr.fsf@gitster.mtv.corp.google.com","subject":"Re: problem with insider build for windows and git","fromName":"Johannes Schindelin","fromEmail":"johannes.schindelin@gmx.de","sentAt":"2017-01-19T19:54:02Z","receivedAt":"2017-01-19T20:02:12Z","isPatch":false,"sender":{"key":"johannes.schindelin@gmx.de","avatar":"https://avatars.githubusercontent.com/u/127790?v=4"},"body":"Hi Junio,\n\nOn Wed, 18 Jan 2017, Junio C Hamano wrote:\n\n> Aside from the \"ouch, one topic has merged earlier iteration, that\n> was merged to 'master', also now merged to 'maint', and we need to\n> follow up on both\" you sent out earlier,\n\nI know of one more \"ouch\" moment where my latest iterations did not get\npicked up: my latest version of the \"Avoid a segmentation fault with\nrenaming merges\" patch did not output an error message in case of !nce\nbecause the code flow will result in more appropriate error messages later\nanyway. I did not provide a follow-up patch for that because the current\nversion in `maint` is not wrong per se.\n\n> are there any other topic that are already in 'master' that should go to\n> 2.11.x track?\n\nPersonally, I would have merged 'nd/config-misc-fixes' into `maint`, I\nguess, and 'jc/abbrev-autoscale-config', and probably also 'jc/latin-1'.\nThe 'rj/git-version-gen-do-not-force-abbrev' topic would be another\ncandidate for inclusion. The 'ah/grammos' strikes me as obvious `maint`\nmaterial, as well as 'ew/svn-fixes'. I have no opinion on the p4 topics\n(five, by my counting), as I have no experience with (or for that matter,\nneed for) Perforce, but Lars might have a strong opinion on those.\n\nHaving said that, these are the topics that *I* would merge into `maint`\nif I maintained Git. I don't, so this is just my opinion, man [*1*].\n\nCiao,\nJohannes\n\nFootnote *1*: While you read that last part of the sentence, imagine me in\nslippers and a bathrobe, with a White Russian in my left hand for which I\nused milk instead of cream (for the White Russian, that is, not for my\nleft hand).\n"},{"id":"309774","messageId":"xmqqshoezt7d.fsf@gitster.mtv.corp.google.com","threadId":"44864","inReplyTo":"alpine.DEB.2.20.1701192032330.3469@virtualbox","subject":"Re: problem with insider build for windows and git","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2017-01-19T20:32:38Z","receivedAt":"2017-01-19T20:37:01Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Johannes Schindelin writes:\n\n>> are there any other topic that are already in 'master' that should go to\n>> 2.11.x track?\n>\n> Personally, I would have merged 'nd/config-misc-fixes' into `maint`, I\n> guess, and 'jc/abbrev-autoscale-config', and probably also 'jc/latin-1'.\n\nThe \"almost ready\" pushout were merging the ones that have been in\n'master' for weeks (including that mingw-isatty topic). These three\nare still on radar, but they were too young and that was the only\nreason why they were not included in the batch.\n\n> The 'rj/git-version-gen-do-not-force-abbrev' topic would be another\n> candidate for inclusion. The 'ah/grammos' strikes me as obvious `maint`\n> material, as well as 'ew/svn-fixes'. \n\nI am holding back rj/git-version-gen-do-not-force-abbrev from 2.11.x\nbefore 2.12 is released because I am a bit reluctant to tweak the\nrelease infractructure in 'maint', before the same tweak hits\n'master' and produces a release.\n\nThe second one will involve translators and that is why it is not\nmarked for back-merging in the draft release notes.\n\nI agree that the svn thing should have been merged to 'maint' in\nthat batch, but I missed it.\n\n> Having said that, these are the topics that *I* would merge into `maint`\n> if I maintained Git. I don't, so this is just my opinion, man [*1*].\n\nYes, your opinion was exactly what was requested, and you gave one\n;-)\n"}]}