{"thread":{"id":"62060","subject":"git untracks my files","startedAt":"2024-09-05T04:52:17Z","lastAt":"2024-09-05T21:12:22Z","messageCount":2,"participants":["russell thamm","brian m. carlson"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"502192","messageId":"SI6PR01MB6833E05D68861E02407F7641FE9D2@SI6PR01MB6833.apcprd01.prod.exchangelabs.com","threadId":"62060","inReplyTo":null,"subject":"git untracks my files","fromName":"russell thamm","fromEmail":"russell.thamm@hotmail.com","sentAt":"2024-09-05T04:51:56Z","receivedAt":"2024-09-05T04:52:17Z","isPatch":false,"sender":{"key":"russell.thamm@hotmail.com","avatar":null},"body":"Under Ubuntu 20.04, when my program modifies one of its log files, git \nmarks it as untracked. Other files that my program modifies are \ncorrectly marked as modified.\n\nThis does not happen under Windows 11 and it didn't use to happen under \nUbuntu.\n\nThank you for filling out a Git bug report!\nPlease answer the following questions to help us understand your issue.\n\nWhat did you do before the bug happened? (Steps to reproduce your issue)\n\nPulled the project, built and ran my program which modified log files.\n\nWhat did you expect to happen? (Expected behavior)\n\nI expected the log files to be marked as modified.\n\nWhat happened instead? (Actual behavior)\n\nThe log files were marked as untracked.\n\nWhat's different between what you expected and what actually happened?\n\nI do not expect git to untrack my files.\n\nAnything else you want to add:\n\nOnly happens on Ubuntu 24.04, and not on Windows 11.\n\nPlease review the rest of the bug report below.\nYou can delete any lines you don't wish to share.\n\n\n[System Info]\ngit version:\ngit version 2.43.0\ncpu: x86_64\nno commit associated with this build\nsizeof-long: 8\nsizeof-size_t: 8\nshell-path: /bin/sh\nuname: Linux 6.8.0-41-generic #41-Ubuntu SMP PREEMPT_DYNAMIC Fri Aug  2 \n20:41:06 UTC 2024 x86_64\ncompiler info: gnuc: 13.2\nlibc info: glibc: 2.39\n$SHELL (typically, interactive shell): /bin/bash\n\n\n[Enabled Hooks]\n\n"},{"id":"502285","messageId":"Ztoere5E8_AV9hvM@tapette.crustytoothpaste.net","threadId":"62060","inReplyTo":"SI6PR01MB6833E05D68861E02407F7641FE9D2@SI6PR01MB6833.apcprd01.prod.exchangelabs.com","subject":"Re: git untracks my files","fromName":"brian m. carlson","fromEmail":"sandals@crustytoothpaste.net","sentAt":"2024-09-05T21:12:13Z","receivedAt":"2024-09-05T21:12:22Z","isPatch":false,"sender":{"key":"sandals@crustytoothpaste.net","avatar":"https://avatars.githubusercontent.com/u/497054?v=4"},"body":"On 2024-09-05 at 04:51:56, russell thamm wrote:\n> Under Ubuntu 20.04, when my program modifies one of its log files, git marks\n> it as untracked. Other files that my program modifies are correctly marked\n> as modified.\n> \n> This does not happen under Windows 11 and it didn't use to happen under\n> Ubuntu.\n> \n> Thank you for filling out a Git bug report!\n> Please answer the following questions to help us understand your issue.\n> \n> What did you do before the bug happened? (Steps to reproduce your issue)\n> \n> Pulled the project, built and ran my program which modified log files.\n> \n> What did you expect to happen? (Expected behavior)\n> \n> I expected the log files to be marked as modified.\n> \n> What happened instead? (Actual behavior)\n> \n> The log files were marked as untracked.\n> \n> What's different between what you expected and what actually happened?\n> \n> I do not expect git to untrack my files.\n> \n> Anything else you want to add:\n> \n> Only happens on Ubuntu 24.04, and not on Windows 11.\n\nI'm not sure that there's enough information for us to go on here.  Are\nyou sure the file name is exactly the same, including in case and, if\nrelevant, how it uses Unicode composition in the file system?  Note that\nUbuntu, as with most Unix systems, is case sensitive, and Windows is not\nby default.\n\nCan you provide us with an example shell script that can reproduce the\nproblem, or a repository that we can clone and build relatively easily\nthat demonstrates the problem?  If we had such a reproduction example,\nit would be easy for us to see what the difference in behaviour is\nacross systems and fix it if it's a bug (or explain what's going on if\nit's not).\n\nOne final note: typically log files don't belong in a repository, since\nthey're artifacts from building or running the program, which tend to\ncause needless diff noise and merge conflicts.  Thus, usually we'd\nrecommend that this output not even be stored in a repository at all, so\nthe files should be untracked and ignored.\n-- \nbrian m. carlson (they/them or he/him)\nToronto, Ontario, CA\n"}]}