Git

TwitterFacebook
Get flash to fully experience Pearltrees
http://mislav.uniqpath.com/2013/02/merge-vs-rebase/

Git merge vs. rebase

The short: git pull --rebase instead of git pull git rebase -i @{u} before git push (on “feature”) git merge master to make feature compatible with latest master (on “master”) git merge --no-ff feature to ship a feature However if “feature” contains only 1 commit, avoid the merge commit: (on “master”) git cherry-pick feature The long:
La collection mémento enfin en version numérique ! Utilisé depuis plus de 5 ans pour le noyau Linux, Git est le système révolutionnaire de gestion de versions, plébiscité chez les développeurs modernes. Co-écrit par deux développeurs Git et Debian, ce mémento aidera les développeurs qui découvrent la gestion de versions avec Git à optimiser leurs processus d'édition collaborative et à exploiter sans risque la puissance de cet outil, qui succède à CVS et SVN. Le développeur verra rappelées toutes les commandes de création, d'exploration, de modification, d'annulation et de restauration de code ou de branche, avec un schéma illustrant les commandes liées aux cinq grands lieux de Git : le cache ( stash ), le répertoire de travail, l'index, le dépôt local et le dépôt distant. Les auteurs complètent le mémento de nombreux conseils d'utilisation - ce qu'est un bon commit, comment l'écrire... http://izibook.eyrolles.com/produit/2517/9782212181111/

Mémento Git à 100% - - De Raphaël Hertzog et Pierre Habouzit (EAN13 : 9782212181111)

A successful Git branching model » nvie.com

http://nvie.com/posts/a-successful-git-branching-model/ Published: January 05, 2010 In this post I present the development model that I’ve introduced for all of my projects (both at work and private) about a year ago, and which has turned out to be very successful. I’ve been meaning to write about it for a while now, but I’ve never really found the time to do so thoroughly, until now. http://nvie.com/posts/a-successful-git-branching-model/
https://help.github.com/articles/generating-ssh-keys If you have decided not to use the recommended HTTPS method , we can use SSH keys to establish a secure connection between your computer and GitHub. The steps below will walk you through generating an SSH key and then adding the public key to your GitHub account. Step 1: Check for SSH keys

Generating SSH keys (Linux)

Everyday GIT With 20 Commands Or So

A standalone individual developer does not exchange patches with other people, and works alone in a single repository, using the following commands. Examples Use a tarball as a starting point for a new repository. https://www.kernel.org/pub/software/scm/git/docs/everyday.html
http://wiki.eclipse.org/EGit/Git_For_Eclipse_Users From Eclipsepedia This post is aimed at those who have been using Eclipse for a while, and probably have been using either the baked-in CVS or external SVN providers to store their source code. The content of the post is about Git: what it means to you, as an Eclipse user, and specifically, how it affects how you obtain or work with projects from Eclipse.org. This post is not about the relative merits of Git over CVS/SVN, or of Git versus other distributed version control systems (DVCS) like Mercurial (Hg).

EGit/Git For Eclipse Users

From Eclipsepedia Overview If you're new to Git or distributed version control systems generally, then you might want to read Git for Eclipse Users first. More background and details can be found in the on-line book Pro Git . If there you are coming from CVS, you can find common CVS workflows for Git Platform-releng/Git Workflows . Basic Tutorial: Adding a project to version control http://wiki.eclipse.org/EGit/User_Guide

EGit/User Guide