Excerpts from David Martin (Staff)'s message of 2016-02-29 17:29:19 +0100: > One reason why I like to use graphical clients such as SourceTree for Git. It > hides much of the pain.
i introduce new git users to gitk right from the start. (though any other tool that visualizes the branch history would work just as well) for any complex git operation, look at the visual layout of the branches before and after. gitk makes that very easy as it keeps the old branch around even if you have moved it. that way you learn what to expect from different operations, and it is also easier to make sense of them. (what does git rebase do?) once you get the idea, for any operation you are unsure about, try to imagine how the change should look like. then check that it does look as expected. if not, investigate what went wrong. in the beginning you will do this for every operation, later only for the complex ones. i still do this myself. it is reassuring to see that graph looking exactly like i expect it to be. greetings, martin. -- eKita - the online platform for your entire academic life -- chief engineer eKita.co pike programmer pike.lysator.liu.se caudium.net societyserver.org secretary beijinglug.org mentor fossasia.org foresight developer foresightlinux.org realss.com unix sysadmin Martin Bähr working in china http://societyserver.org/mbaehr/ _______________________________________________ Discuss mailing list [email protected] http://lists.software-carpentry.org/mailman/listinfo/discuss_lists.software-carpentry.org
