{"thread":{"id":"39703","subject":"Untracked files when git status executed on a new folder","startedAt":"2015-06-23T15:19:21Z","lastAt":"2015-06-24T15:28:45Z","messageCount":3,"participants":["Víctor Martín Hernández","Johannes Löthberg"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"264630","messageId":"1435072761.15867.38.camel@aliga.ieec.uab.es","threadId":"39703","inReplyTo":null,"subject":"Untracked files when git status executed on a new folder","fromName":"Víctor Martín Hernández","fromEmail":"vmartin@aliga.ieec.uab.es","sentAt":"2015-06-23T15:19:21Z","receivedAt":"2015-06-23T15:19:21Z","isPatch":false,"sender":{"key":"vmartin@aliga.ieec.uab.es","avatar":null},"body":"Hi all.\nToday I've had an unexpected behaviour that I'm not sure if is a bug or\nI'm not doing git best practices... (surely the latest...)\nThe sequence of actions is :\n\n1. create a new subfolder of my local repository branch\n2. cd to this new folder, and create a new file\n3. execute git status from the new folder\n\nDoing that, the new folder doesn't appear as untracked.\n\n4. cd ..\n5. git status\nIn this case, the new folder appears.\n\nIf I create a new folder on the same level that the new one created in\nstep 1, cd into it, and execute git status, the folder created in step 1\nappears as untracked.\n\nAfter step 3 I have executed git commit and git push to the remote, and\nlater another user has realized that the new file was not present.\n\nPlease let me know if you understand my explanation, and if it's a bug\nor just that I'm not as experienced as I'd like with git ;)\n\nTHANKS!!\nVíctor\n\n-- \n---\nVíctor Martín Hernández\n\nR&D Software Engineer\nInstituto de Ciencias del Espacio (ICE/CSIC), and \nInstitut d'Estudis Espacials de Catalunya (IEEC)\n\nCampus UAB, Carrer de Can Magrans, s/n\n08193  Bellaterra (Cerdanyola del Vallès) - Barcelona\nTel. : +34 93 586 8782\nWeb:   http://gwart.ice.cat/\n"},{"id":"264633","messageId":"20150623165453.GA9265@leeloo.kyriasis.com","threadId":"39703","inReplyTo":"1435072761.15867.38.camel@aliga.ieec.uab.es","subject":"Re: Untracked files when git status executed on a new folder","fromName":"Johannes Löthberg","fromEmail":"johannes@kyriasis.com","sentAt":"2015-06-23T16:54:53Z","receivedAt":"2015-06-23T16:54:53Z","isPatch":false,"sender":{"key":"johannes@kyriasis.com","avatar":"https://gravatar.com/avatar/af2dea1b1759403329a1b7eaa28a07b5c5d1901e9f55723103d6324ffb7737ae?d=mp&s=160"},"body":"On 23/06, Víctor Martín Hernández wrote:\n>Hi all.\n>Today I've had an unexpected behaviour that I'm not sure if is a bug or\n>I'm not doing git best practices... (surely the latest...)\n>The sequence of actions is :\n>\n>1. create a new subfolder of my local repository branch\n>2. cd to this new folder, and create a new file\n>3. execute git status from the new folder\n>\n>Doing that, the new folder doesn't appear as untracked.\n>\n>4. cd ..\n>5. git status\n>In this case, the new folder appears.\n>\n>If I create a new folder on the same level that the new one created in\n>step 1, cd into it, and execute git status, the folder created in step 1\n>appears as untracked.\n>\n\nCan't reproduce on Git 2.4.4/Linux, which Git version and platform are \nyou using?\n\n-- \nSincerely,\n  Johannes Löthberg\n  PGP Key ID: 0x50FB9B273A9D0BB5\n  https://theos.kyriasis.com/~kyrias/\n"},{"id":"264732","messageId":"1435159725.19750.7.camel@aliga.ieec.uab.es","threadId":"39703","inReplyTo":"20150623165453.GA9265@leeloo.kyriasis.com","subject":"Re: Untracked files when git status executed on a new folder","fromName":"Víctor Martín Hernández","fromEmail":"vmartin@aliga.ieec.uab.es","sentAt":"2015-06-24T15:28:45Z","receivedAt":"2015-06-24T15:28:45Z","isPatch":false,"sender":{"key":"vmartin@aliga.ieec.uab.es","avatar":null},"body":"Hi all,\nsorry for not having sent these informations in my first e-mail.\nI'm working on a Debian Jessie laptop, with git version 2.1.4. \nI watched the same behavior in a workmate's laptop which uses last\nversion of Ubuntu, but now I cannot contact him to get git version.\n\nAfger \"apt-get update\" and \"apg-get install --only-upgrade git\", the\nresponse is that I have the latest git version, what sounds strange to\nme if you say you use version 2.4.4.\n\n\nThanks!!\n\nVíctor\n\n\n \n\nOn Tue, 2015-06-23 at 18:54 +0200, Johannes Löthberg wrote:\n> On 23/06, Víctor Martín Hernández wrote:\n> >Hi all.\n> >Today I've had an unexpected behaviour that I'm not sure if is a bug or\n> >I'm not doing git best practices... (surely the latest...)\n> >The sequence of actions is :\n> >\n> >1. create a new subfolder of my local repository branch\n> >2. cd to this new folder, and create a new file\n> >3. execute git status from the new folder\n> >\n> >Doing that, the new folder doesn't appear as untracked.\n> >\n> >4. cd ..\n> >5. git status\n> >In this case, the new folder appears.\n> >\n> >If I create a new folder on the same level that the new one created in\n> >step 1, cd into it, and execute git status, the folder created in step 1\n> >appears as untracked.\n> >\n> \n> Can't reproduce on Git 2.4.4/Linux, which Git version and platform are \n> you using?\n> \n\n-- \n---\nVíctor Martín Hernández\n\nR&D Software Engineer\nInstituto de Ciencias del Espacio (ICE/CSIC), and \nInstitut d'Estudis Espacials de Catalunya (IEEC)\n\nCampus UAB, Carrer de Can Magrans, s/n\n08193  Bellaterra (Cerdanyola del Vallès) - Barcelona\nTel. : +34 93 586 8782\nWeb:   http://gwart.ice.cat/\n"}]}