From: Wink Saville <wink@saville.com>
To: Steven Walter <stevenrwalter@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: git-svn segmetation fault
Date: Sat, 02 Feb 2008 10:56:40 -0800 [thread overview]
Message-ID: <47A4BCE8.5030308@saville.com> (raw)
In-Reply-To: <20080202160332.GA25945@dervierte>
Steven Walter wrote:
> On Fri, Feb 01, 2008 at 07:55:20PM -0800, Wink Saville wrote:
>
>>> Can you show the contents of .git/config ?
>>>
>>>
> [...]
>
>> [svn-remote "svn"]
>> url = https://async-msgcomp.googlecode.com/svn/trunk
>> fetch = :refs/remotes/git-svn
>>
>
> There's your problem. The url line should only contain the SVN root.
> If you change it thusly:
>
> [svn-remote "svn"]
> url = https://async-msgcomp.googlecode.com/svn
> fetch = trunk:refs/remotes/git-svn
>
> It will no longer segfault. I had the same issue with a repository of
>
> my own.
>
<I did that but a rebase command resulted in: />
wink@ic2d1:$ git svn rebase
Unable to determine upstream SVN information from working tree history
<I've bee using git-svn for a few days without trouble. Do I need
the do another "git svn clone" using the base url rather than
pointing to the trunk? />
next prev parent reply other threads:[~2008-02-02 18:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-01 22:32 git-svn segmetation fault Wink Saville
2008-02-02 0:50 ` Wink Saville
2008-02-02 3:42 ` Steven Walter
2008-02-02 3:55 ` Wink Saville
2008-02-02 16:03 ` Steven Walter
2008-02-02 18:56 ` Wink Saville [this message]
2008-02-02 21:03 ` Steven Walter
2008-02-03 1:21 ` Wink Saville
2008-02-03 2:42 ` Steven Walter
2008-02-03 21:42 ` Wink Saville
2008-02-02 4:06 ` Eric Wong
2008-02-02 4:53 ` Wink Saville
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=47A4BCE8.5030308@saville.com \
--to=wink@saville.com \
--cc=git@vger.kernel.org \
--cc=stevenrwalter@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.