From: Duy Nguyen <pclouds@gmail.com>
To: hultqvist@silentorbit.com
Cc: Junio C Hamano <gitster@pobox.com>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: Temporary git files for the gitdir created on a separate drive in workdir
Date: Sat, 8 Sep 2018 15:09:09 +0200 [thread overview]
Message-ID: <CACsJy8AMaUmWO2zi9+Dpr9_ZHE7A0rSs63h646w4uokyKRAdUg@mail.gmail.com> (raw)
In-Reply-To: <CAJmnt9ZOCJfGFJ98xD17BYU1P=nRZ=eG16Oj5DjTMaF7H6WTvg@mail.gmail.com>
On Sat, Sep 8, 2018 at 11:28 AM Hultqvist <hultqvist@silentorbit.com> 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.
--
Duy
next prev parent reply other threads:[~2018-09-08 13:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-07 6:24 Temporary git files for the gitdir created on a separate drive in workdir Hultqvist
2018-09-07 16:48 ` Junio C Hamano
2018-09-08 6:08 ` Duy Nguyen
2018-09-08 9:31 ` Hultqvist
2018-09-08 13:09 ` Duy Nguyen [this message]
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=CACsJy8AMaUmWO2zi9+Dpr9_ZHE7A0rSs63h646w4uokyKRAdUg@mail.gmail.com \
--to=pclouds@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=hultqvist@silentorbit.com \
/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.