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

Re: Git: Unexpected behaviour?

From
Alexey Shumkin <alex.crezoff@gmail.com>
Date
Nov 12, 2011, 08:32 UTC
Message-ID
<20111112123234.17ab4426@zappedws>
In-Reply-To
<1321044904175-6986736.post@n2.nabble.com>

the same situation and question were discussed and explained one month earlier take a look http://thread.gmane.org/gmane.comp.version-control.git/183464

Show 73 quoted lines
> Unexpected git behaviour
> 
> ---
> # First create a local git repo
> 
> $mkdir gitexample
> $git config --global user.name "my name"
> $git config --global user.email "me@me.com"
> $git init
> $git add .
> $git commit -m 'initial commit'
> 
> # Create/Edit an empty file
> $vi readme.txt
> 
> # add a single line: "this was added in the master branch."
> $git commit -a
> 
> # create and checkout a new branch (from master)
> $git branch test
> $git checkout test
> 
> # edit the readme.txt file and do not commit
> # add the text:  "this was added in the test branch.", save and exit
> $vi readme.txt
> 
> #now switch back to master
> $git checkout master
> $cat readme.txt
> 
> #You will see both lines in the master.  
> 
> Question #1:
> 	Why was this line added in the *master branch?
> 
> 
> --- even further surprising
> In the master branch, now do a commit
> $git commit -a
> 
> cat readme.txt ( you will see the line in the master now that was
> added in the test branch )
> 
> Question #2:
> 	Why did this happen?
> 
> # Now switch back to the test branch
> $git checkout test
> $cat readme.txt
> 
> You will only see the one line: "This was added in the master branch"
> 
> Question #3:
> 	Why did this happen?
> 
> and NOT the line added in that branch: "this was added in the test
> branch" <= this line is gone
> 
> What is the reason for this?
> 
> 1) Why do I see uncommitted changes in the branches made off master
> in the master branch?
> 2) Why, if I commit them in the master, do the disappear in the
> branch in which they were made?
> 
> This is confusing, I would think the * master branch would be left
> untouched.  This would solve issue #2.
> 
> 
> --
> View this message in context:
> http://git.661346.n2.nabble.com/Git-Unexpected-behaviour-tp6986736p6986736.html
> Sent from the git mailing list archive at Nabble.com.
Previous: Jakub NarebskiNext: Eugene Sajine
Message 13 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.