Projects tagged ‘mercurial’ and ‘vcs’

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.

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]

vcs-load-dirs is a tool to automate and simplify the loading of software into version control systems. It is designed primarily for importing from a non-version-controlled upstream, such as processing ... [More] release tarballs. While a bit of scripting can help some version control systems achieve a basic version of this, vcs-load-dirs often does better than that, especially concerning renames. vcs-load-dirs supports baz (bazaar), darcs, git, mercurial (hg), svk, and tla (arch). [Less]

A plugin for bzr which allows pulling from (and eventually pushing to) hg repositories.

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.

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]

IntroductionThe goal of this project is to collect Python based Mercurial hooks. DocumentationIn order to be able to use the hooks provided by hghooklib you need to make sure hghooklib directory is ... [More] in your PYTHONPATH. See the ChangeLog for version information. HooksCurrently, the following hooks are available: Hook Description CheckGpgSig Ensures only changesets signed with GnuPG are pushed to a repository. ForceOneHead Ensures only one head is in the repository. Further ReadingHere are some links which describe Mercurial hooks in more detail: http://www.selenic.com/mercurial/hgrc.5.html#hooks http://mercurial.selenic.com/wiki/Hook http://hgbook.red-bean.com/read/handling-repository-events-with-hooks.html [Less]

Yet another VCS browser (like ViewVC) and a kind of analyzer providing multiple statistics about repository content and developer activities. Targeted to work with Subversion, GIT and Mercurial. ... [More] Currently at the planning and 'proof of concept' phase. Here comes the requirement page. [Less]

Semantic diff and merge tool based on format-aware transformations to and from abstract parse trees: Avoid merge conflicts because of meaningless "flat file" differences like reformatted whitespace ... [More] and line endings. Allow developers to use personal formatting conventions locally while seamlessly enforcing project-wide conventions in the code base. Designed with mercurial in mind; works with any diff3-compatible vcs or dvcs. Eventually, merge binary formats! [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]