git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wink Saville <wink@saville.com>
To: Steven Walter <stevenrwalter@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: git-svn segmetation fault
Date: Fri, 01 Feb 2008 19:55:20 -0800	[thread overview]
Message-ID: <47A3E9A8.1060102@saville.com> (raw)
In-Reply-To: <20080202034258.GA27814@dervierte>

Steven Walter wrote:
> On Fri, Feb 01, 2008 at 04:50:55PM -0800, Wink Saville wrote:
>   
>> Wink Saville wrote:
>>     
>>> I was doing an git-svn dcommit and got a seg fault. The first
>>> phase of updating svn completed and then it seg faulted on the
>>> second. So I suspect I'm out of sync and need to recover,
>>> any guidance appreciated.
>>>       
>
> Can you show the contents of .git/config ?
>   
wink@ic2d1:$ cat .git/config
[core]
        repositoryformatversion = 0
        filemode = true
        bare = false
        logallrefupdates = true
[svn-remote "svn"]
        url = https://async-msgcomp.googlecode.com/svn/trunk
        fetch = :refs/remotes/git-svn
[gui]
        geometry = 999x958+1767+172 407 407
[remote "origin"]
        url = git://192.168.0.8/async-msgcomp.git
        fetch = +refs/heads/*:refs/remotes/origin/*
[merge]
        tool = kdiff3
wink@ic2d1:$

  reply	other threads:[~2008-02-02  3:55 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 [this message]
2008-02-02 16:03       ` Steven Walter
2008-02-02 18:56         ` Wink Saville
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=47A3E9A8.1060102@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 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).