Johannes Schindelin wrote:Well, Git is not the easiest tool on the market to learn. For people used to centralized systems such as RCS/CVS/Subversion, many concepts are truly alien. I've recently experienced a transition at our company from MKS/SI (a RCS derivative) to Subversion, and the mental gap was for many users HUGE. Had we done the transition from MKS/SI to Git, I'm sure several user's brains would have exploded. From my perspective, the concept I found most difficult to grasp at the very beginning was how the index worked, and many of the introductory texts on Git that I looked through only very brielfy explained the purpose of the index: Why is it there? Why is it called "index"? How does it fit into a typical workflow? Having a CVS/Subversion background, it took a while for me to really assimilate the concept. -- /Jesper -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
| monstr | [PATCH 27/56] microblaze_v2: support for a.out |
| Andrew Morton | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| mdew . | Re: [patch] CFS scheduler, v4 |
| Gabriel C | Re: 2.6.21-mm1 |
git: | |
| Gerrit Renker | [PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side) |
| Willy Tarreau | Re: [PATCH] tcp: splice as many packets as possible at once |
| Linus Torvalds | Re: [GIT]: Networking |
| Jarek Poplawski | [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
