Hi Dinesh,

all files that are listed in "untracked files" and "changes not staged for
commit" when you use the command git status will follow you when you change
branch. If you don't want it, you need to commit the changes before
changing branch.


William Seiti Mizuta
@williammizuta
Caelum | Ensino e Inovação
www.caelum.com.br


On Thu, Jul 4, 2013 at 1:45 PM, Dinesh Vijayakumar <dinece...@gmail.com>wrote:

> Hello Git-users,
>      I've a question regarding the use of multiple local branches.
>
> Let's say, I've created a branch b1 and made some changes like adding a
> new file to the branch b1 after checking it out.
>
> Then , I stage the file but not commit it.
>
> Now I find myself a need to create another branch to work on a high
> severity issue.
>
> So, I checkout local master branch and create another b2 from master.
>
> Now when I switch to b2, git shows the new file which is added to branch
> b1.
>
> Shouldnt it replace the contents of my working directory with the contents
> of parent branch master ?  Instead it shows the new file when i do git
> status.
>
>
> Can you please explain how does this work ?
>
>
>
> Thanks,
> Dinesh.
>
>  --
> You received this message because you are subscribed to the Google Groups
> "Git for human beings" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to git-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>

-- 
You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to git-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to