Since this thread started I haven't seen a single file mentioned being created, Usually they appear during work days when there is more activity. I've never seen the files created directly, only a larger amount of them once in a while. I will run process monitor and get back once I find out more. Den lör 8 sep. 2018 kl 15:44 skrev Duy Nguyen <pclouds@xxxxxxxxx>: > > On Sat, Sep 8, 2018 at 3:09 PM Duy Nguyen <pclouds@xxxxxxxxx> wrote: > > > > On Sat, Sep 8, 2018 at 11:28 AM Hultqvist <hultqvist@xxxxxxxxxxxxxxx> wrote: > > > > > > The bash commands are using a git and bash bundle that was installed > > > in parallel with gitextensions(a gui for git) > > > > > > G:\Min enhet> set GIT_TRACE_SETUP=1 > > > G:\Min enhet> git st > > > 10:40:28.881927 trace.c:318 setup: git_dir: > > > C:/Users/hultqvist/Drive.git > > > 10:40:28.881927 trace.c:319 setup: git_common_dir: > > > C:/Users/hultqvist/Drive.git > > > 10:40:28.881927 trace.c:320 setup: worktree: G:/Min enhet > > > 10:40:28.881927 trace.c:321 setup: cwd: G:/Min enhet > > > 10:40:28.881927 trace.c:322 setup: prefix: (null) > > > 10:40:28.882930 chdir-notify.c:67 setup: chdir from 'G:/Min > > > enhet' to 'G:/Min enhet' > > > > Unfortunately this looks good. Whenever those files 'index', > > 'config'... are created, they should always be created in > > C:\Users\hultqvist\Drive.git, not G:\Min enhet, including their > > temporary versions. I don't know if there are any more changes on the > > windows fork that could affect this though, I only checked git.git. > > BTW do you notice these files showing up after any particular command > or they're always there after cloning? Perhaps some command got the > ".git" directory discovery wrong and assumed $GIT_DIR=$GIT_WORK_TREE. > We have a much bigger problem then. > -- > Duy
