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

Re: Git: Unexpected behaviour?

From
JJvsrvcs <jvsrvcs@gmail.com>
Date
Nov 11, 2011, 21:09 UTC
Message-ID
<1321045782702-6986770.post@n2.nabble.com>
In-Reply-To
<1321044904175-6986736.post@n2.nabble.com>

The thing is that I want my 'master' branch' to reflect what is in the 'master' repo - we are using another versioning control system than git for the master for the moment.

I want to be able to switch to the master at any moment, do an update there with the primary versioning system in use, and get all others commits and merge down to my branch from time to time.

It seems to me that this behaviour corrupts the master branch, reflecting a change in the master branch that I did not want or expect.

so I suppose the correct work flow would to be *ALWAYS*, commit on the branch you are on before switching to another branch? I think this would solve the problem.

This just seems a bit odd. I did not commit on the branch, I switched and it's on the master now. At any rate, I can work with it, just need to know the correct work flow I should take before switching to another branch, and that seems to be *ALWAYS* commit before switching to get the expected behaviour that seems normal to me.

-- View this message in context: http://git.661346.n2.nabble.com/Git-Unexpected-behaviour-tp6986736p6986770.html Sent from the git mailing list archive at Nabble.com.

Previous: Carlos Martín NietoNext: Taylor Hedberg
Message 3 of 14 in “Git: Unexpected behaviour?”
  1. JvsrvcsNov 11, 2011
  2. Carlos Martín NietoNov 11, 2011
  3. JvsrvcsNov 11, 2011
  4. Taylor HedbergNov 11, 2011
  5. Gelonida NNov 11, 2011
  6. Chris PackhamNov 11, 2011
  7. J.V.Nov 12, 2011
  8. Chris PackhamNov 12, 2011
  9. Junio C HamanoNov 12, 2011
  10. Martin von ZweigbergkNov 14, 2011
  11. Junio C HamanoNov 14, 2011
  12. Jakub NarebskiNov 14, 2011
  13. Alexey ShumkinNov 12, 2011
  14. Eugene SajineNov 11, 2011

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.