{"thread":{"id":"42222","subject":"possible problem / bug","startedAt":"2016-05-05T02:19:10Z","lastAt":"2016-05-13T11:39:04Z","messageCount":2,"participants":["Bryant Bernstein","Johannes Schindelin"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"285553","messageId":"CAPpP+uW=ReKkUnz4PMEyhchcafd0qtgSZ_Qg0Hq77k4u+aPUyQ@mail.gmail.com","threadId":"42222","inReplyTo":null,"subject":"possible problem / bug","fromName":"Bryant Bernstein","fromEmail":"bryant.bernstein@gmail.com","sentAt":"2016-05-05T02:19:10Z","receivedAt":"2016-05-05T02:19:10Z","isPatch":false,"sender":{"key":"bryant.bernstein@gmail.com","avatar":null},"body":"Both windows and linux support links but both git and the git bash\nseem to have a problem with them.\n\nIn my source, (originally on Linux) I have a link in my source\ndirectory to a config file which I normally import into python.  This\nallows me to have something.py pointing to config.txt .  config.txt\ncan be opened by an editor and something.py can be imported into a\npython shell.\n\nThis worked in Linux alone and on windows  as both platforms support\nlinks.  But if I use git to bring my code from linux to windows I end\nup with a file that contains the path to the target file.\n\nThen I went to try to see what git bash would do with a link.\n\nI created a file and a link to it using ln -s\nThis created a copy of the file I wanted to link to.\n\nWhat do you think?\nShould this work better?\n\nBryant Bernstein\n+ 61 419 323 378\n"},{"id":"286446","messageId":"alpine.DEB.2.20.1605131338480.4092@virtualbox","threadId":"42222","inReplyTo":"CAPpP+uW=ReKkUnz4PMEyhchcafd0qtgSZ_Qg0Hq77k4u+aPUyQ@mail.gmail.com","subject":"Re: possible problem / bug","fromName":"Johannes Schindelin","fromEmail":"johannes.schindelin@gmx.de","sentAt":"2016-05-13T11:39:04Z","receivedAt":"2016-05-13T11:39:04Z","isPatch":false,"sender":{"key":"johannes.schindelin@gmx.de","avatar":"https://avatars.githubusercontent.com/u/127790?v=4"},"body":"Hi Bryant,\n\nOn Thu, 5 May 2016, Bryant Bernstein wrote:\n\n> Both windows and linux support links but both git and the git bash\n> seem to have a problem with them.\n> \n> In my source, (originally on Linux) I have a link in my source\n> directory to a config file which I normally import into python.  This\n> allows me to have something.py pointing to config.txt .  config.txt\n> can be opened by an editor and something.py can be imported into a\n> python shell.\n> \n> This worked in Linux alone and on windows  as both platforms support\n> links.  But if I use git to bring my code from linux to windows I end\n> up with a file that contains the path to the target file.\n> \n> Then I went to try to see what git bash would do with a link.\n> \n> I created a file and a link to it using ln -s\n> This created a copy of the file I wanted to link to.\n> \n> What do you think?\n> Should this work better?\n\nSee https://github.com/git-for-windows/git/wiki/Symbolic-Links\n\nCiao,\nJohannes\n"}]}