rerere is not just a command, but a transverse behavior of Git. For it to be active, you need at least one of two conditions to be met:
The rerere.enabled configuration setting is set to true
Your repo contains a rerere database (you have a .git/rr-cache directory)
I can’t quite fathom a situation where having rerere enabled is a bad idea, so I recommend you go ahead and enable it globally:
git config --global rerere.enabled true
There are situations where it is ueful to checkout multiple repositories, which might use different revision control systems, and operate upon them as a group. This is what the mr tool was designed for.
The mr tool allows you to operate upon multiple repositoresi, regardless of whether they use git, mercurial, bzr, darcs, etc.
=====================================
BONUS: PKGBUILD à jour:
Maintainer: Jimmy Tang jtang@tchpc.tcd.ie
cafai
pkgname=mr-git
pkgver=20150211
pkgrel=1
pkgdesc="The mr(1) command can checkout, update, or perform other actions on a set of repositories as if they were one combined respository."
arch=('i686' 'x86_64')
url="http://joeyh.name/code/mr/"
license=('GPL')
makedepends=('git')
depends=('perl' 'perl-libwww' 'perl-html-parser' 'perl-uri')
optdepends=('git: support for git repositories'
'cvs: support for cvs repositories'
'svn: support for subversion repositories'
'mercurial: support for mercurial repositories'
'bzr: support for bzr repositories'
'darcs: support for darcs repositories')
_gitroot="https://github.com/joeyh/myrepos"
_gitname="myrepos"
pkgver() {
cd "$srcdir"/$_gitname
git log -1 --format="%cd.g%h" --date=short | sed 's/-/./g'
}
build() {
cd "$srcdir"
msg "Connecting to GIT server...."
if [ -d $_gitname ] ; then
cd $_gitname && git pull origin
msg "The local files are updated."
else
git clone $_gitroot
fi
msg "GIT checkout done or server timeout"
msg "Starting make..."
}
package() {
rm -rf "$srcdir/$_gitname-build"
git clone "$srcdir/$_gitname" "$srcdir/$_gitname-build"
cd "$srcdir/$_gitname-build"
#
BUILD HERE
#
make || exit 1
make test || exit 1
install -d -m 0755 $pkgdir/usr/share/man/man1 $pkgdir/usr/bin $pkgdir/usr/lib
install -Dm 755 mr webcheckout $pkgdir/usr/bin
install -D mr.1 webcheckout.1 $pkgdir/usr/share/man/man1
install -D lib/* $pkgdir/usr/lib
#git-fake-bare git-svn unison
}
vim:set ts=2 sw=2 et:
Gitrob is a command line tool that can help organizations and security professionals find such sensitive information. The tool will iterate over all public organization and member repositories and match filenames against a range of patterns for files that typically contain sensitive or dangerous information.
Some day you or a collaborator may accidentally commit sensitive data, such as a password or SSH key, into a Git repository. Although you can remove the file from the latest commit with git rm, the file will still exist in the repository's history. Fortunately, there are other tools that can entirely remove unwanted files from a repository's history. This article will explain how to use two of them: git filter-branch and the BFG Repo-Cleaner.
git-game https://github.com/hgarc014/git-game et regexProgram https://github.com/Liniarc/regexProgram
Be very careful...
The procedure and tools on this page use advanced techniques that involve destructive operations. Make sure you read carefully and take proper precautions to back up your data.
==========
Je viens d'alléger sévérement un repo, à faire méticuleusement.
If you are reading this page, you have decided to, or are considering being part of a study for one or both of the Smeargle or CtrlpSimilar plugins for Vim and Git.
https://github.com/FriedSock/smeargle
https://github.com/FriedSock/ctrlpsimilar
Un petit memo sur la fonction stash de git.
Git peut être assez justement perçu comme une simple structure de données fonctionnelle. Plutôt que de présenter Git comme un outil gestion de versions, nous pouvons voir la gestion de versions comme une résultante de l’utilisation de cette structure de données. Je pense qu’expliquer Git de cette façon exprime mieux la simplicité et la puissance de Git que de comparer son fonctionnement avec celui des systèmes centralisés.
Lorsque l’on voit cela sous cet angle, je trouve que finalement Git est bien plus simple que SVN par exemple. La seule raison pour laquelle Git peut être perçu comme plus complexe est que cette simplicité nous permet d’implémenter des workflows plus intéressants.
Si vous avez toujours trouvé Git intimidant, gardez en mémoire sa structure simple et le fait que dans toute structure de données fonctionnelle, rien n’est jamais réellement perdu et peut être retrouvé (regardez reflog).
What is Tig?
Tig is an ncurses-based text-mode interface for git. It functions mainly as a Git repository browser, but can also assist in staging changes for commit at chunk level and act as a pager for output from various Git commands.
Memo git, expliqué avec des schémas.
Toujours utile
Git log bien plus joli à lire
Git Immersion is a guided tour that walks through the fundamentals of Git, inspired by the premise that to know a thing is to do it.
This is the Git reference site. This is meant to be a quick reference for learning and remembering the most important and commonly used Git commands. The commands are organized into sections of the type of operation you may be trying to do, and will present the common options and commands needed to accomplish these common tasks.
Each section will link to the next section, so it can be used as a tutorial. Every page will also link to more in-depth Git documentation such as the offical manual pages and relevant sections in the Pro Git book, so you can learn more about any of the commands. First, we'll start with thinking about source code management like Git does.
The entire Pro Git book, written by Scott Chacon and published by Apress, is available here. All content is licensed under the Creative Commons Attribution Non Commercial Share Alike 3.0 license. Print versions of the book are available on Amazon.com.
Le livre de référence en Français