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

git push rejected due being behind after git svn dcommit without any changes local/remote

From
HSHenning Sprang <henning.sprang@gmail.com>
Date
May 21, 2014, 16:13 UTC
Message-ID
<CAB10+LtnAiCCiMdrULvioxc-UBQufKD4AzOphvE8bAdq7en04g@mail.gmail.com>
Hi,

I have a client that still uses svn, but I decided to version my work on the project with git locally - using git svn to sync the svn and my local git repo.

To have a backup , I additionally push my changes to a remote git repository.

Now, many(maybe every) times when doing the git push to the remote git repository, after having done an svn dcommit to sync to the remote svn, the push gets rejected:

"... Updates were rejected because the tip of your current branch is behind hint: its remote counterpart...."

You'd say, can happen, when some developers work against the remote git repo, others with svn. But I'm the only developer on the project, and no one ever commits to the remote svn nor the remote git repo. So, I'm clueless.

How can I find out what happens and how to prevent that?

Thanks in advance, Henning

-- 
Henning Sprang
http://www.sprang.de
Next: Thomas Ferris Nicolaisen
Message 1 of 3 in “git push rejected due being behind after git svn dcommit without any changes local/remote”
  1. Henning SprangMay 21, 2014
  2. Thomas Ferris NicolaisenMay 21, 2014
  3. Henning SprangMay 23, 2014

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.