From: Hultqvist <hultqvist@silentorbit.com>
To: git@vger.kernel.org
Subject: Temporary git files for the gitdir created on a separate drive in workdir
Date: Fri, 7 Sep 2018 08:24:01 +0200 [thread overview]
Message-ID: <CAJmnt9Yfed1W7F=C+dzac3AEe7nRq2cNP335MepTczboKJNoEg@mail.gmail.com> (raw)
I'm having two types of git repos in separate drives, in this case G:
is a Google Drive File Stream meaning a slow synchronized storage.
First repo:
Workdir: G:\Test1
Gitdir: C:\Test1.git
G:\Test1\.git containing "gitdir: C:\Test1.git"
Second repo:
Workdir: G:\Test2
Gitdir: G:\Test2\.git
In the first repo I see a lot of "master", "config" and "index" files
being created in the root of the workdir.
The nature of the slow sync causes these files to duplicate - not gits fault.
In the second repo no artefacts are noticed.
I understand that the files are first created "somewhere else" to make
an atomic move later.
In the first repo, the nature of being two separate drives appear to
cause the residue.
In the second repo it works right.
Considering that the gitdir could be located on a different drive than
the workdir wouldn't it make more sense to create the temporary files
in a subdirectory inside the gitdir rather tan in the workdir?
Are there any flags or environment variables to control where
temporary files are created?
next reply other threads:[~2018-09-07 6:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-07 6:24 Hultqvist [this message]
2018-09-07 16:48 ` Temporary git files for the gitdir created on a separate drive in workdir Junio C Hamano
2018-09-08 6:08 ` Duy Nguyen
2018-09-08 9:31 ` Hultqvist
2018-09-08 13:09 ` Duy Nguyen
2018-09-08 13:43 ` Duy Nguyen
2018-09-09 15:30 ` Hultqvist
[not found] ` <CAJmnt9YgFNjzZfOW38WbyC-9AK4rtS3P6_dKN6hS1X+y932uiA@mail.gmail.com>
2018-09-10 10:29 ` Hultqvist
2018-09-11 16:09 ` Duy Nguyen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAJmnt9Yfed1W7F=C+dzac3AEe7nRq2cNP335MepTczboKJNoEg@mail.gmail.com' \
--to=hultqvist@silentorbit.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.