git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: "Torsten Bögershausen" <tboegi@web.de>
Cc: thomas.attwood@stfc.ac.uk, peff@peff.net, git@vger.kernel.org
Subject: Re: git 2.11.0 error when pushing to remote located on a windows share
Date: Fri, 23 Dec 2016 18:04:37 +0100 (CET)	[thread overview]
Message-ID: <alpine.DEB.2.20.1612231803530.155951@virtualbox> (raw)
In-Reply-To: <91983cb6-eed8-987d-bdda-c0fe55a9d139@web.de>

[-- Attachment #1: Type: text/plain, Size: 1007 bytes --]

Hi,

On Tue, 6 Dec 2016, Torsten Bögershausen wrote:

> On 2016-12-05 12:05, thomas.attwood@stfc.ac.uk wrote:
> > On Sun, 4 Dec 2016 08:09:14 +0000, Torsten Bögershausen wrote:
> >> There seems to be another issue, which may or may not being related:
> >> https://github.com/git-for-windows/git/issues/979
> > 
> > I think this is the same issue. I've posted my trace command output there as
> > It might be more appropriate:
> > https://github.com/git-for-windows/git/issues/979#issuecomment-264816175
> > 
> Thanks for the trace.
> I think that the problem comes from the "cwd", when a UNC name is used.
> 
> cd //SERVER/share/somedir
> does not work under Windows, the is no chance to change into that directory.
> Does anybody know out of his head why and since when we change the directory
> like this ?
> Or "git bisect" may help.

For the record, Hannes Sixt came up with a patch that fixes #979, and
which already made it into Git for Windows' `master`.

Ciao,
Johannes

      reply	other threads:[~2016-12-23 17:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-02 18:02 git 2.11.0 error when pushing to remote located on a windows share thomas.attwood
2016-12-02 22:37 ` Jeff King
2016-12-04  8:09   ` Torsten Bögershausen
2016-12-05 11:05     ` thomas.attwood
2016-12-06  3:09       ` Torsten Bögershausen
2016-12-23 17:04         ` Johannes Schindelin [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=alpine.DEB.2.20.1612231803530.155951@virtualbox \
    --to=johannes.schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=peff@peff.net \
    --cc=tboegi@web.de \
    --cc=thomas.attwood@stfc.ac.uk \
    /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).