Git Must Die

+2 by Jack W

I see messages like: "To prevent you from losing history, non-fast-forward updates were rejected." What the F is a non-fast-forward update? Is that the best you can come up with? I go to the online manual and get a general sense of what that means (still, the term 'non-fast-forward' is ludicrous).
Still, I can't for the life of me figure out how to recover. I try a 'git pull --rebase origin:master' (WTF kind of command is that) and I get: "You asked me to pull without telling me which branch you want to rebase against, and 'branch.PostEvent.merge' in your configuration file does not tell me, either. Please specify which branch you want to use on the command line andtry again (e.g. 'git pull <repository> <refspec>')."
I then try a 'git pull --rebase origin:master' and the g*ddamn thing just hangs. Holy Christ, I need more pins for my git voodoo doll ... STAT!

Picture of Jack W
+0 by Mark B

Try this:

git checkin --maybe origin:remote:local/master/SUB_HEAD -- master/HEAD --headless -non-fastforward <your sub-module directory root>

Er.. you should check this first before doing this in a real repository, or is that a branch? I get these mixed up.. and then again was it git branch or git checkin, there is no checkin? Ok maybe the sub master root's HEAD needs to be manually reset in an editor to point to the previous sha head that was not fast forwarded but was normal forwarded.. I'm still looking for the command that undoes my screwups so I came up with tar. If you tar a copy of all your work, put that tar file someplace far away from git, then try git for a couple of hours then have not one clue what the hell state you are in, you can rm -rf the entire git directory, untar the saved tree and start over. Flush 2 or 3 hours of your life down the toilet.. God I hate this stupid thing.

Picture of Mark B

Your Reply

466,361,353 Opinions from 72,523,482 People Making Their Opinion Count


© 2013 Amplicate BETA

Amplicate does not endorse any opinion posted on the site. See terms of use.