git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
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: Tue, 11 Sep 2018 18:09:47 +0200	[thread overview]
Message-ID: <CACsJy8DHTbpOmK=cthus3BZ4BtS0YbJS8=K72BCb7=fFx6TPBw@mail.gmail.com> (raw)
In-Reply-To: <CAJmnt9aCfMGejO3B5ctZuCjJnE4K-dA1dwyz1uxoZwRBOJJqpg@mail.gmail.com>

On Mon, Sep 10, 2018 at 12:27 PM Hultqvist <hultqvist@silentorbit.com> wrote:
>
> Sending again without HTML
>
> Den mån 10 sep. 2018 kl 12:28 skrev Hultqvist <hultqvist@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

      reply	other threads:[~2018-09-11 16:10 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
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 [this message]

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CACsJy8DHTbpOmK=cthus3BZ4BtS0YbJS8=K72BCb7=fFx6TPBw@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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).