Projects tagged ‘cvs’ and ‘mercurial’

The BuildBot is a system to automate the compile/test cycle required by most software projects to validate code changes. By automatically rebuilding and testing the tree each time something has ... [More] changed, build problems are pinpointed quickly, before other developers are inconvenienced by the failure. The guilty developer can be identified and harassed without human intervention. By running the builds on a variety of platforms, developers who do not have the facilities to test their changes everywhere before checkin will at least know shortly afterwards whether they have broken the build or not. Warning counts, lint checks, image size, compile time, and other build parameters can be tracked over time, are more visible, and are therefore easier to improve. [Less]

Tailor is a tool to migrate changesets between ArX, Bazaar, Bazaar-NG, CVS, Codeville, Darcs, Git, Mercurial, Monotone, Perforce, Subversion and Tla repositories.

cvs2svn is a Python script that converts a CVS repository to a Subversion repository. It is designed for one-time conversions, not for repeated synchronizations between CVS and Subversion.

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]

Project Builder (aka pb) helps you package your software from your CMS (Subversion or CVS currently) to multiple distributions (mandriva, fedora, openSuSE, debian, ubuntu, gentoo to name a few) either ... [More] locally or using virtual machines (qemu currently). It's written in perl and is derived from the build system made originally for the MondoRescue project, completely rewritten to be project independant and support others such as LinuxCOE or collectl. [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]

Table of Contents NewsIntroductionLicensingOperating SystemsFurther ReadingFinal Notes News .gadget-title { margin-bottom: 2px; } function resizeIframeHandler(opt_height) { var elem = ... [More] document.getElementById(this.f); if (!elem) return; if (!opt_height) { elem.style.height = undefined; } else { opt_height = Math.max(10, opt_height); elem.style.height = opt_height + 'px'; } } gadgets.rpc.register("resize_iframe", resizeIframeHandler); gadgets.rpc.register('set_title', function(title) { var elem = document.getElementById(this.f + '_title'); if (elem) { elem.innerHTML = gadgets.util.escape(title); } }); IntroductionCVS, Mercurial, GIT as well as other well-known version control systems cannot version directories. In other words, you cannot add empty directories! A "workaround" for this issue is to use placeholder files which are placed into empty directories. These placeholder files can then be committed into the repository and will make sure that, upon checkout, the directory tree is entirely reconstructed. This solution is also suggested in the Mercurial FAQ, or in the GIT FAQ, for instance. Note however, that using that workaround might not be a good idea. Creating missing directories during a build process should also be considered as an option. Sometimes a solution where the missing directories are created by some magic is not practicable and people will face the problem of managing such placeholder files. In particular, the problem with using placeholder files is that you need to create them, and delete them, if they are not necessary anymore (because there were added sub-directories or files). With big source trees managing these placeholder files can be cumbersome and error prone. In the past, I had been confronted with such a situation several times. This is why I decided to write an open source tool which can manage the creation/deletion of such placeholder files automatically. It creates placeholder files in all empty "leaf" directories. If later on new files or directories are put into such directories, the placeholder files are not necessary anymore and, thus, are removed automatically. LicensingThis tool is licensed under the GPLv3. Operating SystemsMarkEmptyDirs is written in C# and is designed to be platform independent. Currently, it runs on Mono.NET as well as on Microsoft.NET platform. The following compatibility matrix shows the currently supported operating systems and runtimes. Operating System Supported Runtimes Linux Mono.NET MacOS X Mono.NET Windows Mono.NET, Microsoft.NET Further ReadingGettingStarted describes what you need to do in order to run MarkEmptyDirs. UseCases describes typical use cases for this tool and how to use it. ChangeLog describes what has changed in the different releases. Final NotesIf you like MarkEmptyDirs please digg it, because seeing there is some interest in this tool motivates me to develop it and improve it further :) [Less]