From: Fredrik Gustafsson <iveqy@iveqy.com>
To: Ain Valtin <ain.valtin@gmail.com>
Cc: Fredrik Gustafsson <iveqy@iveqy.com>, git@vger.kernel.org
Subject: Re: separate-git-dir doesn't work with mapped drive
Date: Sat, 19 Oct 2013 13:55:45 +0200 [thread overview]
Message-ID: <20131019115545.GU13967@paksenarrion.iveqy.com> (raw)
In-Reply-To: <CADgy817rrg0s9icaT_QdAWGiRsb6T5eg4LJAc+Q7CdM=Csexkw@mail.gmail.com>
On Sat, Oct 19, 2013 at 02:45:46PM +0300, Ain Valtin wrote:
> On Sat, Oct 19, 2013 at 2:11 PM, Fredrik Gustafsson <iveqy@iveqy.com> wrote:
> >
> > Git has a bad history with mapped drives in windows. It's also usually a
> > bad idea to use git over the network (and most mapped drives are over
> > the network and not local between virt. machines).
> >
> > I would advise not to use this setup since for the past two years that
> > git has sometime worked and sometimes not with this setup. (It's not
> > just seperate git dir, a git dir at all over a smb share have been
> > problematic).
>
> That's a shame :(
> As I wrote I want to use git in a virtual machine and as a extra
> precaution it would be nice to have the repo outside of the VM, on the
> host drive - should the VM not to start up for whatever reason I
> wouldn't lose my repo with it...
>
>
> ain
A better way (if you can afford it) is to have a repo on the virtual
machine and push to a repo on your hostmachine (so that you've two
repos). However your solution "should" work but I personally have had
some problems with that area.
--
Med vänliga hälsningar
Fredrik Gustafsson
tel: 0733-608274
e-post: iveqy@iveqy.com
next prev parent reply other threads:[~2013-10-19 11:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-19 8:49 separate-git-dir doesn't work with mapped drive Ain Valtin
2013-10-19 9:17 ` Duy Nguyen
2013-10-19 11:11 ` Fredrik Gustafsson
2013-10-19 11:45 ` Ain Valtin
2013-10-19 11:55 ` Fredrik Gustafsson [this message]
2013-10-19 15:47 ` Torsten Bögershausen
2013-10-19 20:21 ` Ain Valtin
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=20131019115545.GU13967@paksenarrion.iveqy.com \
--to=iveqy@iveqy.com \
--cc=ain.valtin@gmail.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 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 NNTP newsgroup(s).