On Tuesday, July 3, 2012, jack sparrow wrote:
> I don't understand why each branch has to be related to one
> another. Here's my thought, i should be able to create
> multiple branches each possibly with certain tag version.
> The work done in each branch can be on completely different
> files o
On Wednesday, June 27, 2012 7:00:23 PM UTC+5:30, Peter J Weisberg wrote:
>
> On Tuesday, June 26, 2012, Mostafa Alshrief
> wrote:
> >
> >> If any of the uncommitted changes collide with files changed between
> branches, it will refuse to switch, and ask you to stash the changes first
> >
> > wha
On Tuesday, June 26, 2012, Mostafa Alshrief
wrote:
>
>> If any of the uncommitted changes collide with files changed between
branches, it will refuse to switch, and ask you to stash the changes first
>
> what do you mean by collide with files..?
If A.txt on master is different from A.txt on devel
Hi,
Git will bring along any uncommitted changes when checking out another branch.
It doesn't corrupt or change the branches.
If any of the uncommitted changes collide with files changed between branches,
it will refuse to switch, and ask you to stash the changes first.
--
You received this
i have 2 branches one is the master and other is the develop
i'm working on the 'develop' branch i have made some changes but didn't
commit,
i tried to switched from 'develop' to 'master' with uncommitted changes,
and git switched branches corrupting the 'master' branch with changes from
the
'd
