From: Eric Wong <normalperson@yhbt.net>
To: Russ Dill <russ.dill@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: git-svn+cygwin failed fetch
Date: Wed, 11 Jul 2007 22:48:00 -0700 [thread overview]
Message-ID: <20070712054800.GC29676@muzzle> (raw)
In-Reply-To: <f9d2a5e10707110254j46d1123fuade955f17da0a8c5@mail.gmail.com>
Russ Dill <russ.dill@gmail.com> wrote:
> On 7/11/07, Eric Wong <normalperson@yhbt.net> wrote:
> >Russ Dill <russ.dill@gmail.com> wrote:
> >> [...]/src $ mkdir foo
> >> [...]/src $ cd foo
> >> [...]/src/foo $ git-svn init -t tags -b branches -T trunk
> >> https://www.[...].com/svn/foo/bar/bla
> >> Initialized empty Git repository in .git/
> >> Using higher level of URL: https://www.[...].com/svn/foo/bar/bla =>
> >> https://www.[...].com/svn/foo
> >>
> >> [...]/src/foo $ git-svn fetch
> >> config --get svn-remote.svn.url: command returned error: 1
> >>
> >> [...]/src/foo $ git config --get svn-remote.svn.url
> >> https://www.[...].com/svn/foo
> >
> >Sorry, I can't help here other than recommending a real UNIX with
> >fork + pipe + exec and all that fun stuff.
> >
> >git-svn relies heavily[1] on both input and output pipes of the
> >safer-but-made-for-UNIX fork + pipe + exec(@list) variety, so I suspect
> >this is just the tip of the iceberg for Windows incompatibilies with
> >git-svn...
>
> Its actually reading and writing quite a bit of stuff from the config
> file, so why this one simple command would fail eludes me. Especially
> since it wrote it there in the first place. If I comment out the
> command_oneline and hardcode the value I know it should return,
> git-fetch runs. Its actually been running for several hours now.
Wow. That's a pleasant surprise that anything in git-svn works at all
on cygwin. I was almost certain git-svn on Windows was a hopeless cause
from other chatter I had heard on the mailing list.
command_oneline() is used everywhere in that code, so I'm at a total loss
as to why it would fail in one place. Can you put a the following lines
right before where it was failing?
print "GIT_CONFIG: $ENV{GIT_CONFIG} | GIT_DIR: $ENV{GIT_DIR}\n";
system('cat', "$ENV{GIT_DIR}/config");
And tell me what it outputs?
--
Eric Wong
next prev parent reply other threads:[~2007-07-12 5:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-10 18:06 git-svn+cygwin failed fetch Russ Dill
2007-07-11 9:06 ` Eric Wong
2007-07-11 9:54 ` Russ Dill
2007-07-12 5:48 ` Eric Wong [this message]
2007-07-12 17:49 ` Russ Dill
2007-07-12 18:27 ` Eric Wong
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=20070712054800.GC29676@muzzle \
--to=normalperson@yhbt.net \
--cc=git@vger.kernel.org \
--cc=russ.dill@gmail.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 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).