GUI Clients Git comes with built-in GUI tools for committing (git-gui) and browsing (gitk), but there are several third-party tools for users looking for platform-specific experience. Only show GUIs for my OS (Linux)0Linux GUIs are highlighted below ↓ TowerPlatforms: MacPrice: $59/user (Free 30 day trial) GitboxPlatforms: MacPrice: $14.99 Git ExtensionsPlatforms: WindowsPrice: Free git-colaPlatforms: Windows, Mac, LinuxPrice: Free GitEyePlatforms: Windows, Mac, LinuxPrice: Free gitgPlatforms: LinuxPrice: Free
Git Magic Git est un couteau suisse de la gestion de versions. Un outil de gestion de révisions multi-usage, pratique et fiable, dont la flexibilité en rend l’apprentissage pas si simple, sans parler de le maîtriser ! Comme Arthur C. Plutôt que de rentrer dans le détails, nous donnons des instructions pour obtenir tel ou tel effet. Je reste modeste devant le travail fourni par tant de monde pour traduire ces pages. Dustin Sallings, Alberto Bertogli, James Cameron, Douglas Livingstone, Michael Budde, Richard Albury, Tarmigan, Derek Mahar, Frode Aannevik, Keith Rarick, Andy Somerville, Ralf Recker, Øyvind A. François Marier maintient le paquet Debian, créé à l’origine par Daniel Baumarr. Ma gratitude va également à beaucoup d’autres pour leurs encouragements et compliments. Si par erreur je vous ai oublié, merci de me le signaler ou, plus simplement, envoyez-moi un patch ! Hébergement Git gratuit héberge des projets libres. Un grand merci à ces sites pour l’hébergement de ce guide.
What are the basic clearcase concepts every developer should know Git et Subversion Aujourd'hui, la majorité des projets de développement libre et un grand nombre de projets dans les sociétés utilisent Subversion pour gérer leur code source. C'est le VCS libre le plus populaire depuis une bonne décennie. Il est aussi très similaire à CVS qui a été le grand chef des gestionnaires de source avant lui. Une des grandes fonctionnalités de Git est sa passerelle vers Subversion, git svn. git svn La commande de base dans Git pour toutes les commandes de passerelle est git svn. Il est important de noter que lorsque vous utilisez git svn, vous interagissez avec Subversion qui est un système bien moins sophistiqué que Git. Ne réécrivez pas votre historique avant d'essayer de pousser à nouveau et ne poussez pas en parallèle dans un dépôt Git pour collaborer avec vos collègues développant avec Git. Installation Pour montrer cette fonctionnalité, il faut un serveur SVN sur lequel vous avez des droits en écriture. En préparation, créez un nouveau dépôt local Subversion : Démarrage
8 ways to share your git repository This blogpost provides a summary of different ways to share a git repository. Depending on your needs you can opt for different solutions. Preparation:Git enable a simple project-X Let's say you have project called project-X that you have been working on, on your local machine. $ cd $HOME/project-X # git init enables the git repository $ git init # You add the readme file to the repository $ git add README # You commit your changed to your local repository $ git commit -a -m 'Added README' this will give you a .git directory in the project-X directory , ready to use in this tutorial Share it over a file share Instead of having people reference your local repository, you can put your repository on a file share. Preparing the repository Pushing your local repository to the shared repository Controlling access As we are dealing with a fileshare, permissions are handled by filesystem permissions.
Mercurial, Subversion, and Wesley Snipes People keep asking me why I don't talk more about Mercurial in this series of blog entries. There's a simple answer to that question: Mercurial isn't very interesting. Wait, that didn't come out quite right. Let me try again: Git is Wesley Snipes. Mercurial is Denzel Washington Hmm, that probably needs further explanation. I am the founder of a version control software company. As part of that effort, I have undertaken an exploration of the DVCS world. The one where I gripe about Git's index The one where I whine about the way Git allows developers to rearrange the DAG The one where it looks like I am against DAG-based version control but I'm really not The one where I fuss about DVCSes that try to act like centralized tools The one where I complain that DVCSes have a lousy story when it comes to bug-tracking The one where I lament that I want to like Darcs but I can't The one where I speculate cluelessly about why Git is so fast Why am I using these tools if I don't like them?
How to git-svn clone the last n revisions from a Subversion repository Git Book - Distributed Workflows Unlike Centralized Version Control Systems (CVCSs), the distributed nature of Git allows you to be far more flexible in how developers collaborate on projects. In centralized systems, every developer is a node working more or less equally on a central hub. In Git, however, every developer is potentially both a node and a hub — that is, every developer can both contribute code to other repositories and maintain a public repository on which others can base their work and which they can contribute to. This opens a vast range of workflow possibilities for your project and/or your team, so I’ll cover a few common paradigms that take advantage of this flexibility. I’ll go over the strengths and possible weaknesses of each design; you can choose a single one to use, or you can mix and match features from each. Centralized Workflow In centralized systems, there is generally a single collaboration model—the centralized workflow. Figure 5-1. Integration-Manager Workflow Figure 5-2. Figure 5-3.
Diff Between Mercurial and Git Install SmartGit via PPA in Ubuntu 13.10/13.04/12.04/Linux Mint This tutorial will show you how to install SmartGit/HG easily via PPA in Ubuntu 13.10, Ubuntu 13.04, Ubuntu 12.04, Ubuntu 12.10 and Linux Mint. As you may know, SmartGit/Hg is a graphical Git and Mercurial client which can also connect to SVN repositories. SmartGit/Hg runs on Linux, Mac OS X (10.5 or newer) and Windows (XP or newer). SmartGit/Hg depends on Java Runtime Environment. Once Java properly installed, press Ctrl+Alt+T on your keyboard to open terminal. sudo add-apt-repository ppa:eugenesan/ppa sudo apt-get update sudo apt-get install smartgithg
Git bare vs. non-bare repositories Posted by: Kim N. Lesmer on 09.10.2010 The Git revision control system has something called a "bare" and a "non-bare" repository. NB! The other day I was working with Git and I got the following error after having tried to push some changes back to a remote repository that I had created. I didn't understand this error and being used to how Mercurial works, this didn't make any sense, so I did some diggin. In the ideal world of distributed revision control there is no central repository. In the real world a central repository with push access is sometimes necessary and all the different distributed revision control systems allows this, but the way they deal with a push are very different. In a distributed revision control system you work with a local repository that contains both the working tree and the revision history. In Git you can create such a repository with the following command: $ mkdir my_repo $ cd my_repo $ git init In Bazaar it is done the same way: $ hg init my_repo