On Mon, Sep 10, 2018 at 12:27 PM Hultqvist <hultqv...@silentorbit.com> wrote: > > Sending again without HTML > > Den mån 10 sep. 2018 kl 12:28 skrev Hultqvist <hultqv...@silentorbit.com>: > > > > First I need to correct my previous observations.
Please don't top-post. > > Today there appeared new set of config files in the root. > > I looked into a few of them and found that their content doesn't match that > > of the repo at "G:/Min enhet". > > Instead separate files had content from separate git repos within the G > > drive. > > These repos are not like the one we're discussed previously, they are > > completely within G: using a classical .git directory. > > > > I guess git is creating the temporary files as close as possible to the > > root, since "G:\" can't be written to, only "G:\Min enhet". and then copy > > them to the final destination which in this case is the same drive. No. Those files should always be created inside the ".git" directory, wherever it is. Failing to creating a file in there is usually a serious error and the command will abort. Unless there is a bug lurking around of course, but I can't nail it down with just code audit. Since the content of those files does not look like from "G:\Min enhet" repo, do you know which repo they belong to (and where those repo and worktree are)? I ask because if these are submodules of "G:\Min enhet" for example, then we need to head another direction. Or if they are completely unrelated to "G:\Min enhet", oh boy... -- Duy
