Projects tagged ‘mercurial’ and ‘svn’

OpenGrok is a fast and usable source code search and cross reference engine. It helps you search, cross-reference and navigate your source tree. It can understand various program file formats and ... [More] version control histories like Mercurial, Git, SCCS, RCS, CVS, Subversion, Teamware, ClearCase, Perforce and Bazaar. In other words it lets you grok (profoundly understand) the open source, hence the name OpenGrok. It is written in Java. [Less]

The Ohloh Source Control Management library is an abstraction layer for source control management systems, allowing an application to interoperate with various SCMs using a single interface. It was ... [More] originally developed at Ohloh, and is used to generate the reports at www.ohloh.net. [Less]

Transifex is a system that facilitates the process of submitting translations in various version control systems (VCS) by acting as a proxy for these submissions for a whole translation community. The ... [More] name literally means "translation-builder" (from the latin verb facere). [Less]

A way to integrate VCS-agnostic repository browsing into Django apps. Initially, Subversion and Git will be supported (and hopefully Mercurial as well), but if anyone is interested in supplying other functionality, please let us know.

Python Multiple Project Managament System for Subversion (SNV) / GIT / Mercurial based on web.py, sqlobject and Lasagna2 (visie project) using tickets and roundups for manage your staff.

AboutThis extension for mercurial allow commiting/updating svn sandbox (including .svn folder) with hg to allow both svn and hg work with it correctly. CReDS refers to Centralized Repository with ... [More] Distributed Sandboxes. It is an approach of working with two Revision Controls when svn sandbox of central repository is commited into mercurial with all its content (including .svn folder). Thus developer is available to commit into mercurial extrimelly often, and switch beetwen implementing of different features, but at the same time put into svn only production ready changes. DownloadsYou can get stable version from svn:hgsvnbox.py or latest available version from hg:hgsvnbox.py [Less]

gedit-vcsMission StatementTo create, with the community, a set of version control system integration plugins for gedit to allow for the version control of files from within gedit. FeaturesCommon ... [More] interface for all VCS plugins to adhere to View which files are up to date, modified, or in conflict with the latest repository revision Update files from a repository Commit local changes to a repository Delete or move files within a repository View differences between local revisions and those in a repository Resolve conflicts in files Development Statusgedit-vcs is in the requirements and design phases of development. There is not yet a production release of any of the plugins. Requirementsgedit trunk This Project is FreeIn the side panel of this page, you will find that this project and its source code are licensed under the GNU Lesser Public License v3. Essentially what this means is that this project is provided free of charge to use and extend under the conditions of the GPLv3 license. [Less]

Soon.

IntroductionWhen trying to develop small to medium size projects, you often skip setting up big and complicated CI (Continuous Integration) tools such as Buildbot. Who would want to set up an almost ... [More] enterprise tool, that could drive away hours of development when all you need is something simple to continuously check for errors every time you commit code to a repository? Main objectiveTo run CUSCO once in one terminal while you work on your IDE or on another terminal. You commit your code and you see your tests in real time. Dependencies and VersionsBefore running everything please NOTE that CUSCO was developed with Python 2.6 You will also need: Pylint Nose CUSCO will not run unless these dependencies are met. OptionsFor full options run: python cusco.py --helpYou will always need to supply a path. To start serving right away: python cusco.py -p /path/to/directoryCurrent Limitationscusco will only run with HG (Mercurial) and has limited options. For now, it will only run the tests against an existing path with code and will return the results via Nose at the terminal. Feature ListHave a Master Cusco Daemon that runs somewhere else and you can connect remotely. Configuration files for different scenarios. You always need the options! SVN support. Email alerts Multi-threaded tests for several instances/scenarios [Less]