git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: git-svn+cygwin failed fetch

From
Russ Dill <russ.dill@gmail.com>
Date
Jul 11, 2007, 09:54 UTC
Message-ID
<f9d2a5e10707110254j46d1123fuade955f17da0a8c5@mail.gmail.com>
In-Reply-To
<20070711090600.GB29676@muzzle>
On 7/11/07, Eric Wong <normalperson@yhbt.net> wrote:
Show 22 quoted lines
> 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.

Previous: Eric WongNext: Eric Wong
Message 3 of 6 in “git-svn+cygwin failed fetch”
  1. Russ DillJul 10, 2007
  2. Eric WongJul 11, 2007
  3. Russ DillJul 11, 2007
  4. Eric WongJul 12, 2007
  5. Russ DillJul 12, 2007
  6. Eric WongJul 12, 2007

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.