<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"><html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><meta name="generator" content="AsciiDoc 8.2.7"><title>qct(1)</title></head><body><h1>qct(1)</h1><p><strong>Steve Borho</strong><br /><tt><<a href="mailto:steve@borho.org">steve@borho.org</a>></tt><br /></p><hr /><h2><a name="_name"></a>NAME</h2><p>qct - Qt Commit Tool</p><hr /><h2><a name="_synopsis"></a>SYNOPSIS</h2><p><em>qct</em> [VCS]</p><hr /><h2><a name="_description"></a>DESCRIPTION</h2><p>The qct(1) command provides a common GUI commit dialog for many revisioncontrol systems across many platforms, including Linux/UNIX, MacOSX, andMicrosoft Windows.</p><hr /><h2><a name="_version_control_systems"></a>VERSION CONTROL SYSTEMS</h2><dl><dt>Mercurial</dt><dd><p> [—hg|-h] Qct supports both the simple repository model and the Mercurial Queue patch maintenance model. When MQ patches are applied, qct will present a patch refresh user interface. Consult README.mercurial for more details.</p></dd><dt>Bazaar</dt><dd><p> [—bzr|-b] Bazaar support is complete, but could use some polishing. Qct can run as a bazaar plugin. Consult README.bazaar for more details.</p></dd><dt>Perforce</dt><dd><p> [—p4|-4] Perforce support is complete, if somewhat restrictive. On Windows, you must override P4DIFF with a command line diff tool. Consult README.perforce for more details.</p></dd><dt>CVS</dt><dd><p> [—cvs|-c] CVS support is feature complete, but not well tested. Consult README.cvs for more details.</p></dd><dt>Monotone</dt><dd><p> [—mtn|-m] Monotone support is feature complete, but not well tested. Consult README.monotone for more details.</p></dd><dt>Subversion</dt><dd><p> [—svn|-s] Subversion support is not very well tested at this time, so consider it alpha quality. Consult README.subversion for more details.</p></dd><dt>Git</dt><dd><p> [—cg] Git repositories are only supported via the Cogito front-end interface, which must be installed in order for Qct to work properly. Consult README.git for more details.</p></dd></dl><hr /><h2><a name="_vcs_integration"></a>VCS INTEGRATION</h2><p>Qct can run as a plugin inside both Mercurial and Bazaar. Pleaseconsult the packaged INSTALL file and each plugin's built-in help formore information.</p><hr /><h2><a name="_sign_off_messages"></a>SIGN OFF MESSAGES</h2><p>If you require a sign-off (or other) message to be appended to allof your commit messages, you can specify this message in the Qctpreferences dialog. The sign-off message will not show up in thecommit message window, but will be automatically appended to yourmessage when passed to the VCS for commit.</p><hr /><h2><a name="_change_selection"></a>CHANGE SELECTION</h2><p>Qct will allow you to select individual changes made to revisionedfiles, temporarily storing the remaining changes under a .qct/ directoryuntil the commit has been completed. To enable this feature, youmust configure a two-way merge application in the Qct preferencesdialog. Kompare, meld, and kdiff3 are all known to work correctly inthis mode. Any merge application which takes two file-names on thecommand line and allows them to be merged together can be used.</p><hr /><h2><a name="_external_editor"></a>EXTERNAL EDITOR</h2><p>You can register an external editor with the Qct preferences dialog.Your editor will be presented as a context-menu option for allnon-deleted commitable files in the file list.</p><hr /><h2><a name="_external_diff"></a>EXTERNAL DIFF</h2><p>If your VCS supports external diff tools, you may register one of thesewith the Qct preferences dialog. Your diff tool will be offered in thecontext menu of all modified files in your file list. The diff toolwill be provided with the list of selected files so it must be capableof retrieving the file diffs itself, typically by getting them fromyour revision control system.</p><hr /><h2><a name="_files"></a>FILES</h2><dl><dt>~/.config/vcs/qct</dt><dd><p> This file contains persistent data stored by Qct between invocations. It is not meant to be user modified.</p></dd></dl><hr /><h2><a name="_bugs"></a>BUGS</h2><p>Probably lots, please send them to be via e-mail when you find them.Patches (or mercurial bundles) are always welcome.</p><p>Windows has a known limitation of 32Kbytes for it's command line. SinceQct operates directly with the VCS command line tools, it is possible torun into this limit.</p><hr /><h2><a name="_author"></a>AUTHOR</h2><p>Written by Steve Borho <<a href="mailto:steve@borho.org">steve@borho.org</a>></p><hr /><h2><a name="_resources"></a>RESOURCES</h2><p><a href="http://qct.sourceforge.net/">Web Page</a><a href="http://qct.sourceforge.net/hg/qct">Source code repository</a></p><hr /><h2><a name="_copying"></a>COPYING</h2><p>Copyright (C) 2006 Steve BorhoFree use of this software is granted under the terms of the GNU GeneralPublic License (GPL)</p><p></p><p></p><hr /><p><small>Last updated 2008-11-30 07:56:54 SGT</small></p></body></html>