Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

cvscheck(1) [centos man page]

CVSCHECK(1)							  [FIXME: manual]						       CVSCHECK(1)

NAME
cvscheck - Offline status report for files in a checked-out CVS module. SYNOPSIS
cvscheck [dir] DESCRIPTION
cvscheck prints information about the status of your local CVS checkout without communicating with the server. This means it is extremely fast and does not require a network connection. The given directory and all of its subdirectories will be processed recursively. If no directory is given, the current directory and its recursed subdirectories will be used. Each file with an interesting status will be printed with a status character in front of its name. The status characters are as follows. ? foobar.c The file is not known to CVS M foobar.c The file is definitely locally modified m foobar.c The file might have local changes. You should diff with the server to make sure. C foobar.c The file has a CVS conflict and therefore cannot be committed. U foobar.c This file is in CVS but is missing in your local checkout. T foobar.c This file has an unusual sticky CVS tag. A foobar.c You have done a cvs add for this file, but have not yet committed it. R foobar.c You have done a cvs rm for this file, but have not yet committed it. This utility is part of the KDE Software Development Kit. SEE ALSO
cvs(1) AUTHORS
cvscheck was written by Dirk Muller<mueller@kde.org> and Sirtaj.Singh.Kang; <taj@kde.org> This manual page was prepared by Ben Burton<bab@debian.org> for the Debian GNU/Linux system (but may be used by others). [FIXME: source] March 8, 2003 CVSCHECK(1)

Check Out this Related Man Page

CVS-DEBC(1)						      General Commands Manual						       CVS-DEBC(1)

NAME
cvs-debc - view contents of a cvs-buildpackage/cvs-debuild generated package SYNOPSIS
cvs-debc [options] [package ...] DESCRIPTION
cvs-debc is run from the CVS working directory after cvs-buildpackage or cvs-debuild. It uses the cvs-buildpackage system to locate the .changes file generated in that run. It then displays information about the .deb files which were generated in that run, by running dpkg- deb -I and dpkg-deb -c on every .deb archive listed in the .changes file, assuming that all of the .deb archives live in the same directory as the .changes file. It is useful for ensuring that the expected files have ended up in the Debian package. If a list of packages is given on the command line, then only those debs with names in this list of packages will be processed. Note that unlike cvs-buildpackage, the only way to specify the source package name is with the -P option; you cannot simply have it as the last command-line parameter. OPTIONS
All current cvs-buildpackage options are silently accepted; however, only the ones listed below have any effect. For more details on all of them, see the cvs-buildpackage(1) manpage. -adebian-architecture, -tGNU-system-type See dpkg-architecture(1) for a description of these options. They affect the search for the .changes file. They are provided to mimic the behaviour of dpkg-buildpackage when determining the name of the .changes file. -Mmodule The name of the CVS module. -Ppackage The name of the package. -Vversion The version number of the package. -Ttag The CVS tag to use for exporting sources. -Rroot directory Root of the original sources archive. -Wwork directory The full path name for the cvs-buildpackage working directory. -xprefix This option provides the CVS default module prefix. --help, --version Show help message and version information respectively. SEE ALSO
cvs-buildpackage(1), cvs-debi(1), cvs-debuild(1) and debc(1). AUTHOR
cvs-buildpackage was written by Manoj Srivastava, and the current version of debi was written by Julian Gilbey <jdg@debian.org>. They have been combined into this program by Julian Gilbey. DEBIAN
Debian Utilities CVS-DEBC(1)
Man Page