{"thread":{"id":"44367","subject":"An anomaly, not a bug","startedAt":"2016-10-24T21:46:08Z","lastAt":"2016-10-24T22:47:27Z","messageCount":3,"participants":["m.","Alexei Lozovsky"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"304808","messageId":"20161024214601.GA11699@hostname_variable_in_muttrc","threadId":"44367","inReplyTo":null,"subject":"An anomaly, not a bug","fromName":"m.","fromEmail":"botmetkas@gmail.com","sentAt":"2016-10-24T21:46:01Z","receivedAt":"2016-10-24T21:46:08Z","isPatch":false,"sender":{"key":"botmetkas@gmail.com","avatar":null},"body":"Concerning \".gitignore\", experienced using git 2.10.0\n\nStarting code using one or more spaces or tabs from the left\nmargin will have git reading .gitignore and ignoring(or\nun-ignoring) the command-instruction.\n\nExample: Starting .gitignore\n\n/*\n        # above line is duly read.  Then un-ignoring\n        # something but starting the command further to the\n        # right will have git not reading that line\n\n  !/nottobeignored.file\n\nEnd .gitignore\n\nNote: the comments can be started away from the left margin,\nas normal in all unix-linux configuration files we know of.\nGit follows this behaviour fine.\n\nThe lines containing commands, on the contrary of regular\nconvention cannot be indented by spaces or tabs.  Quite\nunusual, confusing, not in the sense of conventional and\neasily adverted in coding git.\n\nCould be we are missing out on something,\n\nGit command line tool is a functional tool now in our setup\nfor two years, first noticed this alien behaviour in this\nversion of git, on osx, the fink(osx package mananger)\nbinary.\n\n\n"},{"id":"304810","messageId":"CALhvvbYnTf9qqsCFWjgfnynRy9LDEQf=Y++2tQioTKHbaYGHDA@mail.gmail.com","threadId":"44367","inReplyTo":"20161024214601.GA11699@hostname_variable_in_muttrc","subject":"Re: An anomaly, not a bug","fromName":"Alexei Lozovsky","fromEmail":"a.lozovsky@gmail.com","sentAt":"2016-10-24T22:20:47Z","receivedAt":"2016-10-24T22:21:16Z","isPatch":false,"sender":{"key":"a.lozovsky@gmail.com","avatar":"https://gravatar.com/avatar/8bb8ff5ec366dd64bd8e08f768082934513da367ae047bcb0039292e4ed6bda5?d=mp&s=160"},"body":"> Note: the comments can be started away from the left margin,\n> as normal in all unix-linux configuration files we know of.\n> Git follows this behaviour fine.\n\nActually, git reads\n\n    # comment\n\nas 'ignore files with name \"    \" (4 spaces)', and then a comment.\nIt does not ignore the leading whitespace.\n"},{"id":"304812","messageId":"CALhvvbap=-KNHiDvKy4bb9BdWkgbxOjhVXAw+EQpRNXKeqgQFw@mail.gmail.com","threadId":"44367","inReplyTo":"CALhvvbYnTf9qqsCFWjgfnynRy9LDEQf=Y++2tQioTKHbaYGHDA@mail.gmail.com","subject":"Re: An anomaly, not a bug","fromName":"Alexei Lozovsky","fromEmail":"a.lozovsky@gmail.com","sentAt":"2016-10-24T22:47:02Z","receivedAt":"2016-10-24T22:47:27Z","isPatch":false,"sender":{"key":"a.lozovsky@gmail.com","avatar":"https://gravatar.com/avatar/8bb8ff5ec366dd64bd8e08f768082934513da367ae047bcb0039292e4ed6bda5?d=mp&s=160"},"body":"> Actually, git reads\n>\n>     # comment\n>\n> as 'ignore files with name \"    \" (4 spaces)', and then a comment.\n> It does not ignore the leading whitespace.\n\nEven not as a comment, it treats it as literally a filename with\na hash and that comment in it. However, one (usually) does not\nname their files like that, so for all purposes this can be thought\nof as a sort of comment.\n"}]}