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

How to jump between two repositories ...

From
Gg2 <gerald.gutierrez@gmail.com>
Date
Dec 5, 2007, 05:59 UTC
Message-ID
<C6AF7922-B2F7-42EB-B5DD-25353BC0AF2A@gmail.com>
Hello all,

I am currently working on some code at the office that I also want to work with at home. Seems like a good candidate for git. So I created a repository at work and did a "git clone" at home. I've run into some strange behaviour that I don't understand and would appreciate if someone can clarify for me.

Imagine this scenario. At work: git init edit test.c git add test.c git commit

Then at home: git clone <work git url> edit test.c git commit -a git push

At this point, I wanted to push my changes back to my work repository so I can continue work the next day. So at home, I did a git push. I expect that my work repository has the newest material, but I find that when I do "git status" at work the next day, it tells me that my test.c is "modified" and has already staged it for commit. I need to do a "git reset" followed by "git checkout" to update my work folder to the latest stuff.

Totally different from my expectation of the repository knowing that it is out of date and then kindly suggesting that I should do a "git update" of some sort. What piece of understanding am I missing to properly "get" what is going on here, and how am I supposed to properly work with this setup?

Thanks for any help. Gerald.

Next: Shawn O. Pearce
Message 1 of 10 in “How to jump between two repositories ...”
  1. g2Dec 5, 2007
  2. Shawn O. PearceDec 5, 2007
  3. J. Bruce FieldsDec 5, 2007
  4. Andreas EricssonDec 5, 2007
  5. g2Dec 5, 2007
  6. Andreas EricssonDec 5, 2007
  7. Väinö JärveläDec 5, 2007
  8. g2Dec 5, 2007
  9. Steven GrimmDec 5, 2007
  10. Väinö JärveläDec 5, 2007

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.