Re: Data Integrity & un-Commited Branches

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



"Brian Scott Dobrovodsky" <brian@xxxxxxxxxxx> writes:

> Just started using Git today and I already shot myself in the foot.

Thanks.  Input from new people who has never seen git is very
valuable to spot where our software and/or documentation is
confusing, as long timer on this list have all lost git
virginity long time ago.

> ..., when working within a newly created branch, you are allowed to
> switch branches without committing. The un-commited changes will then
> be present in all other branches....

You take local changes with you when you switch branches.
This happens consistently, even to the point that you are not
allowed to switch branches if your local changes conflict with
the differences between the branches you are switching from and
to.

This may be inconsistent with how you _thought_ switching
branches in git _might_ work.  We may need to update the
tutorial (you did read tutorial, didn't you?) to make sure new
people would understand what switching branches in git _means_
before they even learn that git supports multiple branches and
allows switching branches.  Can you point out where you got the
impression that switching branches while having local changes
would blow away your local changes and give you a clean slate?


-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]

  Powered by Linux