je le garde sous le coude pour les personnes qui ne comprennent pas bien, article très bien fait
-
http://images.math.cnrs.fr/J-ai-saute-une-tranche.html?lang=frHEAD^ is the revision before the current
HEAD~2 is the same as HEAD^^ and the revision before HEAD^
-
https://coderwall.com/p/wjlqvw/git-revision-magic-like-a-bossDon Norman
If don’t recognize it is different from mastering complexity
-
http://opennetsummit.org/archives/oct11/shenker-tue.pdfgit branch -a --sort=-committerdate
-
https://links.infomee.fr/?zqUo2QComment perdre 30 min
:set backupcopy=yes
When you want to modify a file, you have two options, each with its benefits and drawbacks.
You can overwrite the file in place. This does not use any extra space, and conserves the hard links, permissions and any other attribute beyond the content of the existing file. The major drawback of doing this is that if anything happens while the file is being written (the application crashes, or the power goes out), you end up with a partially written file.
You can write the new version of the file to a new file with a different name, then move it into place. This uses more space and breaks hard links, and if you have write permissions on a file but not on the directory it contains, you can't do it at all. On the flip side, the old version of the file is atomically replaced by the new version, so at every point in time the file name points to a valid, complete version of the file.
http://vimdoc.sourceforge.net/htmldoc/options.html#%27backup%27
-
http://stackoverflow.com/questions/11043534/edit-a-file-in-place-in-vimJe l'aime bien cet olivier, j'ai découvert son blog au tout début, j'étais en BTS donc 2009, j'ai commencé avec le bouquin la semaine de 4h et j'ai en lu une dizaine suggéré. J'aime bien alterner les lecture fiction et non fiction, ça change un peu et on apprends des choses même si c'est souvent du bon sens, on découvre d'autres manières de voir les choses
-
http://www.des-livres-pour-changer-de-vie.fr/ce-que-ma-apporte-mon-defi-de-lire-52-livres-en-52-semaines-le-bilan-7-ans-apres/je découvre ce plugin vim qui a l'air juste magique pour interagir avec git
-
http://vimcasts.org/episodes/fugitive-vim-working-with-the-git-index/docker run --rm -it -u $(id -u) -v "${PWD}:/data" -w /data ruby:2.3 \
bundle package --all
-
http://blog.slashdeploy.com/2016/11/07/docker-build-container-pattern/Une vue pratique pour comparer les instances ec2
-
http://www.ec2instances.info/il faut que je me fasse au workflow "Branch updater"
-
https://confluence.atlassian.com/bamboo/using-plan-branches-289276872.htmlThe -m option specifies the parent number. This is because a merge commit has more than one parent, and Git does not know automatically which parent was the mainline, and which parent was the branch you want to un-merge.
When you view a merge commit in the output of git log, you will see its parents listed on the line that begins with Merge:
commit 8f937c683929b08379097828c8a04350b9b8e183
Merge: 8989ee0 7c6b236
Author: Ben James ben@example.com
Date: Wed Aug 17 22:49:41 2011 +0100
Merge branch 'gh-pages'
Conflicts:
README
In this situation, git revert 8f937c6 -m 1 will get you the tree as it was in 8989ee0, and git revert -m 2 will reinstate the tree as it was in 7c6b236.
-
http://stackoverflow.com/questions/7099833/how-to-revert-a-merge-commit-thats-already-pushed-to-remote-branch