[perrin@whisper TESTGIT]$ git svn --version git-svn version 1.5.3.rc2.4.g726f9 (svn 1.2.3) I get the "post commit" email from our SVN central server, so it appears that on the SVN side the commit worked? I tried running git svn with --verbose, but that did not print out any more error messages (besides the seg fault). Thanks, Perrin ----- Original Message ---- From: Eric Wong <eric@xxxxxxxxxxxxxx> To: Perrin Meyer <perrinmeyer@xxxxxxxxx> Cc: git@xxxxxxxxxxxxxxx Sent: Wednesday, July 18, 2007 12:34:50 AM Subject: Re: git svn dcommit seg fault Perrin Meyer <perrinmeyer@xxxxxxxxx> wrote: > > I'm able to clone svn repo's fine with > > $ git svn clone https://svn.eng.msli.com/perrin/trunk/TESTGIT/ . > > and I'm then able to use git commit to commit local changes, but > when I try > > $ git svn dcommit > > I get > > [perrin@whisper TESTGIT]$ git svn dcommit > M test.c > Committed r717 > Segmentation fault > As far as I can tell, the commit worked fine (verified by trying 'svn > update' on another box). > > I've tried git version 1.5.2.3, 1.5.3-rc2, and the latest build, and > all give the seg fault. > > I'm guessing it has something to do with using the https connection to > svn? I primarily work with https repositories using git-svn and I haven't seen any segfaults in a while. Which version of the SVN libraries do you have? (git-svn --version will tell you). -- Eric Wong - 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 - 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
