On 7/11/07, Eric Wong <normalperson@xxxxxxxx> wrote:
Russ Dill <russ.dill@xxxxxxxxx> 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. - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
