Bazaar v2.0.x Back to iOS Resources
qbzr – Qt dialogs for many Bazaar commands — Bazaar v2.0.x documentation
QBzr is a cross platform, Qt-based front-end for Bazaar, providing GUI applications for many core bzr commands. In addition, it provides several special dialogs and helper commands. Equivalents for core bzr commands have the same names as CLI commands but with a prefix of “q”. QBzr requires Qt/PyQt 4.4.x or later to be installed.
Git
Git – Fast Version Control System
Home of the Git Version Control System and Friends.
Bazaar
Bazaar version control system: easily manage source code on Windows, Ubuntu, GNU/Linux, and Mac OS X.
GitX
ere you can have a look at what GitX looks like. There are screenshots and screencasts for you to enjoy!
SmartGit
SmartGit – The Best Git Gui So Far | Engineered Web
As Git becomes more popular and widely used a GUI becomes even more important. This was especially important when Drupal recently looked at what version control system it was going to switch to. (If you’re interested in the Drupal (unofficial) decision checkout Angie Byrons post on groups.drupal.org).
BzrPlugins
BzrPlugins – Bazaar Version Control
A plugin is an external component for Bazaar that extends Bazaar’s functionality, by adding or replacing code. Plugins are often a way for developers to test new features prior to inclusion in the core codebase. Plugins can do a variety of things, including overriding commands, adding new commands, providing additional network transports, customizing log output, etc. Bazaar’s developers give the plugin architecture a lot of attention, ensuring that it’s one of the most comprehensive revision control plugin systems available.
Bazaar v2.2.2
bzr-svn — Bazaar v2.2.2dev documentation
bzr-svn lets developers use Bazaar as their VCS client on projects still using a central Subversion repository. Access to Subversion repositories is largely transparent, i.e. you can use most bzr commands directly on Subversion repositories exactly the same as if you were using bzr on native Bazaar branches.Many bzr-svn users create a local mirror of the central Subversion trunk, work in local feature branches, and submit their overall change back to Subversion when it is ready to go. This lets them gain many of the advantages of distributed VCS tools without interrupting existing team-wide processes and tool integration hooks currently built on top of Subversion. Indeed, this is a common interim step for teams looking to adopt Bazaar but who are unable to do so yet for timing or non-technical reasons.
Bazaar User Guide
Bazaar User Guide — Bazaar v2.2.2dev documentation
How to use Bazaar.
Bazaar Launchpad
Subversion branch support for Bazaar in Launchpad
This makes it possible to run the standard Bazaar subcommands (“bzr branch”, “bzr log”, “bzr commit”) against local Subversion working copies and remote Subversion repositories.
Bazaar Project Files
To download project files for bazaar.
Git Hosting
Subversion Hosting, Git Hosting, Project Management
Unfuddle is a secure, hosted software development environment providing Git hosting, Subversion hosting, bug and issue tracking, milestones, time tracking, audit trails and more.
Tortoisegit
tortoisegit – Project Hosting on Google Code
It is porting TortoiseSVN to TortoiseGit The latest release 1.5.8.0Please avoid use msysgit 1.7.2.3 with 1.5.3.0If you use 1.2.1.0 or previous version, please uninstall it firstly. 1.5.8.0 use gitdll.dll which from git source code. gitdill.dll will miss if you install 1.5.8.0 over 1.2.1.0 or previous versionThis release can complete regular task, such commit, show log, diff two version, create branch and tag, Create patch and so on. See ReleaseNotesfor detail. Welcome to contribute this project.If you use tortoisegit at win2k environment, please install GDI+ firstly.
Using Bazaar
Using Bazaar on Subversion projects — Bazaar Migration Docs
bzr-svn lets developers use Bazaar as their VCS client on projects still using a central Subversion repository. Access to Subversion repositories is largely transparent, i.e. you can use most bzr commands directly on Subversion repositories exactly the same as if you were using bzr on native Bazaar branches.Many bzr-svn users create a local mirror of the central Subversion trunk, work in local feature branches, and submit their overall change back to Subversion when it is ready to go. This lets them gain many of the advantages of distributed VCS tools without interrupting existing team-wide processes and tool integration hooks currently built on top of Subversion. Indeed, this is a common interim step for teams looking to adopt Bazaar but who are unable to do so yet for timing or non-technical reasons.
