git/list[1] front-page[2] threads[3] people[4] search[5] about
 

more git weirdness (git rebase, merge conflicts

From
JJ.V. <jvsrvcs@gmail.com>
Date
Mar 27, 2013, 18:51 UTC
Message-ID
<51533FB9.7070307@gmail.com>

I have a local/development branch tracked to origin/development. I made no changes to local/dev and did a git pull with rebase, I did not expect any conflicts.

I got a conflict and was thrown onto another branch. I attempted a merge (using IntelliJ) accepting everything from the server but a variable definition was missing for some odd reason and the merge was not successful (merge was resolved but the file would not compile) so I decided to simply go back to my dev branch and figure out how to do a git pull -f (force overwrite of all local files so that I could get my local/dev back into sync with origin/dev.

On my screwed up branch that I was thrust onto:
I typed:
     $git rebase --skip            <= I was stuck in a rebase (rebase 
failed, was thrown onto a tmp branch and thought this would get me out 
of there)

Now I have been sitting here for an hour watching "Applying: <message" scroll by and it looks like the messages are going backwards into the past one by one. What the hell is happening?

     Applying: add log information
     Applying: <previous message
     .... and it goes on and on and on.

All I want to do at this point is to get back to my dev branch and force pull from origin/dev while keeping all local files that have not been added to my local repo.

How do I stop this madness and get back to local dev and force pull from origin/dev <= which is our master.

Any help would be greatly appreciated.
thanks
J.V.
Next: Magnus Bäck
Message 1 of 2 in “more git weirdness (git rebase, merge conflicts”
  1. J.V.Mar 27, 2013
  2. Magnus BäckMar 28, 2013

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.