Une méthode pour ne pas rsync des fichiers qui ont été déplacés dans la source

Et en commentaire une extension à la solution qui m'a l'air pas mal du tout

I use a derivative of this method, by creating a separate hard-links directory with md5-filenames. This gets rid of any duplicate files as well. Any files in this hard links directory with link count 1 are removed. Any files in the albums tree without the same inode to be found in the hard links tree are hard-linked into the hard links tree by using an MD5 of the file. Before I rsync I update the hard links dir, so when my wife decides to make a beautiful photobook and copies and moves lots of photos around, my ADSL doesn't get swamped when backing up my local photo store.

The same script also generates JPG files from Nikon image files (NEF).

This works both on FreeBSD/Linux/UNIX/etc as well as NTFS. Which is nice.

online resources to prepare aws certifications

Via arnaudb

https://github.com/mozilla/geckodriver/releases

HEAD^ is the revision before the current
HEAD~2 is the same as HEAD^^ and the revision before HEAD^

git branch -a --sort=-committerdate

Comment 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

Big-O illustré en ruby

Je 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