There is a point to this story, but it has temporarily escaped my mind...
Contact Me MyFaceBook MyLinkedIn MyGitHub MyTwitter
You are here: Home » Software Development » GIT » Why GIT sucks as a SVN front-end! My Internal Area

Why GIT sucks as a SVN front-end!

I can't go a week without getting this “error”: 

      0 [main] perl 9208 handle_exceptions: Exception: STATUS_ACCESS_VIOLATION
    747 [main] perl 9208 open_stackdumpfile: Dumping stack trace to perl.exe.stackdump

The numbers are always different, but it always when I'm committing changes into a remote SVN repository. It doesn't matter if I use MSYSGIT or Cygwin, the result is the same. I really like using GIT, but the attitude of the developers leaves something to be desired.

The problem is that when this does occur, it corrupts the local repository. It has gotten so bad, that I always backup my GIT repository so that I can recover. I simply delete the repository files, restore from the backup, “rebase” the restored repository, then attempt the operations again.

Copyright © 2022 by Julian Easterling. SOME RIGHTS RESERVED.
Privacy Policy              Terms of Use             


Creative Commons License
Except where otherwise noted, content on this site is
licensed under a Creative Common Attribution-Share Alike 4.0 International License.


All of the opinions expressed on this website are those of Julian Easterling and
do not represent the views of any of my current and previous clients or employers in any way.

If you notice an error on the site or content that has not been properly attributed, bring
it to my attention using the contact page and I will endeavor to fix it as soon as I can.

I accept no responsibility or liability for any damages incurred by following any of
my advice or by using any of the information on my site or of those sites that I link to.