Actually there is no problem because of this issue.
I just want to know why it happens and what is the logic.
On Mon, Aug 24, 2015 at 10:36 PM, Priya K <priyacst at gmail.com> wrote:
Actually I understand the process of stashing.
If we work in a remote repository, this doubt will not arise. But I have
the git repository in my local machine.
When I switch one branch to other branch, if the changes are not
committed, it should show the error "Please, commit your changes or stash
them before you can switch branches".
But in my case that error didn't occur. I understand that without the
error also we can stash the changes.
Actually only this happens when we create and edit any new branches. Once
a branch is ready with some commits, then there is no problem.
Pls try it with your local machine.
On Mon, Aug 24, 2015 at 7:28 PM, Manokaran K <manokaran at gmail.com> wrote:
Its likely that the changes you have made in the new branch is not in an
already tracked file.
_______________________________________________
ILUGC Mailing List:
http://www.ae.iitm.ac.in/mailman/listinfo/ilugc
ILUGC Mailing List Guidelines:
http://ilugc.in/mailinglist-guidelines
--
Regards,
*K. Priya*
*Spoken Tutorial Project*
http://spoken-tutorial.org
*IIT Bombay*