- [InterfacesFrontendsAndTools] page on Monotone wiki
- [Tools that work with Mercurial] page on Mercurial wiki
- [RelatedSoftware|Software that works with darcs] page on Darcs wiki
- [party tools] and [registry] pages on Bazaar-NG wiki
Other programs that *should* be taught to work with Git, but haven't been
[[[#Bugzilla|Bugzilla]]], [[[#Bonsai|Bonsai]]], [[[#Trac|Trac]]], [[[#TWiki|TWiki]]], [[[#scmbug|SCMBug]]], [[[#be|BugsEverywhere]]], [[[#Savane|Savane]]], [[[#libresource|LibreSource]]], [[[#DVC|DVC (Emacs)]]], [[[#PIDA|PIDA]]], [[[#Eric3|Eric3]]], [[[#xxdiff|xxdiff]]], [[[#Dreamweaver|Dreamweaver]]]
Bugzilla (bugtracker)<<Anchor(Bugzilla)>><<Anchor(Bonsai)>>:: !
[] is a "Defect Tracking System" or "Bug-Tracking System". [Bug Tracker] for posting bugs against the mainline Linux kernels is based on Bugzilla.
Patch Viewer is (built in?) an enhancement to Bugzilla designed to provide adequate context for submitted patches through integration with [], [] and CVS. [] is a small piece of Perl-glue to integrate either CVS or Subversion with Bugzilla and CVSWeb or ViewCVS. See also: [[[#scmbug|SCMBug]]] entry below.
It would be nice to have also Git integration, for example referencing commits and tags, perhaps via making (additionally) Bonsai report against Git. Via hooks, this should be possible using []. (Perl)
Trac (bugtracker/wiki/history browser)<<Anchor(Trac)>><<Anchor(GitTrac)>>::
[] is a popular integrated history browser/wiki/bug tracker, which has very recently grown a plugin interface that lets it work with VCS-es besides Subversion. The right place to start is probably the [TracMercurial plugin], since Mercurial uses the same history model as Git. Another right place could be the [GitPlugin], a plugin for Trac to use Git instead of Subversion (and perhaps also [GitwebPlugin]). Using [TracGitPlugin] is not recommended, as it is a hack.
There is also [Trac] project to add Git suport for [], similar to Trac but simpler project (inspiration for Trac).
Another similar project for which would be nice to have Git support is [] and []. (Python for Trac, C for CVSTrac, Ruby on Rails for Collaboa, Java for JIRA).
[] is a flexible, powerful, and easy to use enterprise collaboration platform and knowledge management system. It includes plugins for integration with bug-tracking software: Bugzilla and GNATS. Plugins are developed under CVS and Subversion; moving to Subversion is encouraged. No support for plugin development under Git. (Perl CGI)
SCMBug (SCM with bugtracking integration)<<Anchor(scmbug)>>::
[] is a system that integrates software configuration management (SCM) with bug-tracking. It aims to be a universal tool that will glue any source code version control system (supports CVS and Subversion, no Git support yet) with any bug-tracking system (supports Bugzilla, Mantis and Request Tracker). It is in early version. (Perl)
Bugs Everywhere (bugtracker)<<Anchor(be)>>::
[Everywhere] is a bug-tracker for distributed development. It stores bugreports inside the repository, so the status of bugs are propagated with push/pull/merges, and no glue is needed between the SCM and the Bug Tracker. Has Git support. (Python)
Savane (software hosting system)<<Anchor(Savane)>>::
[] is a web-based software hosting system. Both Savannah ([] and []) and [] use Savane as their software hosting engine. They currently include issue tracking, project member management by roles and individual account maintenance. The issue tracking handles bugs, tasks, support, news and documentation management. It currently supports CVS, Subversion, and GNU Arch. Savannah uses [branch of Savane] which does have [support], but there is no Git support in [] proper yet. (Perl or PHP)
[], another software hosting system, has also plans for Git support (see [revision control support] ticket); currently it supports Subversion and Mercurial ('hg'),
LibreSource (Open Source Versatile Collaborative Distributed Envirionment)<<Anchor(libresource)>>::
[] aims to be distributed version of collaborative environment platforms such as Drupal (CMS) or SourceForge (software development). LibreSource includes its own SCM tool called LibreSource Synchronizer (described as: innovative, simple, united). Since version 2.0 LibreSource integrates the Subversion SCM... which is a bit strange as Subversion is centralized SCM. It would be nice to have integration with Git, which is distributed SCM. (Java J2EE: ObjectWeb Jonas application server)
DVC (Distributed Version Control) (Emacs interface)<<Anchor(DVC)>>::
[] is a project to create a generic library for fancy Emacs interfaces to modern version control systems. Has support for several systems, including (incomplete) support for Git. (Emacs, elisp)
[] is a full featured Python (and Ruby) IDE that is written in PyQt using the QScintilla editor widget. It supports CVS, Subversion and Mercurial. (Python, Qt)
Popular open-source IDE offering typical IDE features for Java, Ruby, C++ and other languages. See NetBeansPlugin for information on a plugin in development. (Java, Swing)
Merge tools <<Anchor(xxdiff)>><<Anchor(KDiff3)>><<Anchor(Kompare)>>::
Perhaps [] (Qt; has CVS and Subversion integration with scripts), [] and/or [] (Kompare is diff only) should also have some VCS support... (Python, GNOME)
Note: Git support for external graphical merge resolution programs has been added into the git development mainline via a new git command, "git mergetool", as of git 1.5.1. git-mergetool currently supports kdiff3, meld, xxdiff, tkdiff, and GNU Emacs's emerge.
[4 Beta] Download the prerelease of the next version of Dreamweaver now and send us your feedback. The Dreamweaver beta will expire soon after the next version of Dreamweaver is available for purchase. I've [in a request] to the Dreamweaver CS4 Forum.
Quickbuild (Continuous Integration build server)
[] for the upcoming 2.0 release. The new 2.0 version allows the writing of plugins for repositories.
Rational Team Concert (Work Item Management / SCM / Build Management / Dev. Environment)
[Team Concert] - A collaborative software development environment. Rational Team Concert enables developers to collaborate together using integrated Planning, Source Control, Work Items, Build, Dashboards, Reports, and Process Support. An example Git integration tutorial can be seen []