From: Tim Chase <git@tim.thechases.com>
To: John Keeping <john@keeping.me.uk>
Cc: git@vger.kernel.org
Subject: Re: Proper URI for "svn clone" on a network share (Win32)
Date: Thu, 15 Aug 2013 06:12:29 -0500 [thread overview]
Message-ID: <20130815061229.24dfe891@bigbox.christie.dr> (raw)
In-Reply-To: <20130815080058.GM2337@serenity.lan>
On 2013-08-15 09:00, John Keeping wrote:
> On Wed, Aug 14, 2013 at 06:26:57PM -0500, Tim Chase wrote:
> > On 2013-08-14 12:49, Tim Chase wrote:
> > > If it makes any difference, this is within a cmd.exe shell (with
> > > $PATH set appropriately so git is being found).
> >
> > Just a follow-up, I tried it within the "bash"ish shell included
> > in the git install and got the same error regarding
> > "/tmp/report.tmp".
>
> It seems that report.tmp is something that SVN creates and for some
> reason the svn on your system is trying to create it in a Unix style
> temporary directory.
>
> What happens if you export TMPDIR=C:/Windows/Temp before running
> git-svn?
Still getting the same results. I tried:
1) cmd.exe with my local temp dir:
c:\temp> TEMPDIR=%TEMP%
c:\temp> git svn clone "file:///x:/path/to/repo/trunk/utils/project1"
2) cmd.exe with the windows temp dir as you specify:
c:\temp> TEMPDIR=c:\windows\temp
c:\temp> git svn clone "file:///x:/path/to/repo/trunk/utils/project1"
3) git's bash.exe with inline variable definition:
$ TEMPDIR=c:/Windows/Temp git svn clone "file:///x:/path/to/repo/trunk/utils/project1"
4) git's bash.exe with exported variable:
$ export TEMPDIR=c:/Windows/Temp
$ git svn clone "file:///x:/path/to/repo/trunk/utils/project1"
All of them died with the complaint about "/tmp/report.tmp"
Thanks for the suggestion though. At least we've determined one
thing that *isn't* the issue ;-)
-tkc
next prev parent reply other threads:[~2013-08-15 11:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-14 17:49 Proper URI for "svn clone" on a network share (Win32) Tim Chase
2013-08-14 23:26 ` Tim Chase
2013-08-15 8:00 ` John Keeping
2013-08-15 11:12 ` Tim Chase [this message]
2013-08-15 11:35 ` John Keeping
2013-08-15 14:21 ` Tim Chase
2013-08-21 0:11 ` Tim Chase
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=20130815061229.24dfe891@bigbox.christie.dr \
--to=git@tim.thechases.com \
--cc=git@vger.kernel.org \
--cc=john@keeping.me.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.
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).