Welcome to Linux Knowledge Base and Tutorial
"The place where you learn linux"
HP & Linux

 Create an AccountHome | Submit News | Your Account  

Tutorial Menu
Linux Tutorial Home
Table of Contents

· Introduction to Operating Systems
· Linux Basics
· Working with the System
· Shells and Utilities
· Editing Files
· Basic Administration
· The Operating System
· The X Windowing System
· The Computer Itself
· Networking
· System Monitoring
· Solving Problems
· Security
· Installing and Upgrading
· Linux and Windows

Glossary
MoreInfo
Man Pages
Linux Topics
Test Your Knowledge

Site Menu
Site Map
FAQ
Copyright Info
Terms of Use
Privacy Info
Disclaimer
WorkBoard
Thanks
Donations
Advertising
Masthead / Impressum
Your Account

Communication
Feedback
Forums
Private Messages
Surveys

Features
HOWTOs
News Archive
Submit News
Topics
User Articles
Web Links

Google
Google


The Web
linux-tutorial.info

Who's Online
There are currently, 226 guest(s) and 0 member(s) that are online.

You are an Anonymous user. You can register for free by clicking here

  

cvsps



SYNOPSIS

       cvsps  [-h] [-x] [-u] [-z <fuzz>] [-g] [-s <patchset>] [-a
       <author>]  [-f  <file>]  [-d  <date1>  [-d  <date2>]]  [-l
       <text>]  [-b  <branch>]  [-r <tag> [-r <tag>]] [-p <direc­
       tory>] [-v] [-t]  [--norc]  [--summary-first]  [--test-log
       <filename>]  [--bkcvs]  [--no-rlog]  [--diff-opts  <option
       string>] [--cvs-direct] [--debuglvl <bitmask>]  [-Z  <com­
       pression>] [--root <cvsroot>] [-q] [<repository>]


DESCRIPTION

       CVSps  is  a program for generating 'patchset' information
       from a CVS repository.  A patchset in this case is defined
       as a set of changes made to a collection of files, and all
       committed at the same time (using a  single  'cvs  commit'
       command).   This information is valuable to seeing the big
       picture of the evolution of  a  cvs  project.   While  cvs
       tracks  revision information, it is often difficult to see
       what changes were committed


OPTIONS

       -h     display usage summary

       -x     ignore (and rebuild) ~/.cvsps/cvsps.cache file

       -u     update ~/.cvsps/cvsps.cache file

       -z <fuzz>
              set the timestamp fuzz factor for identifying patch
              sets

       -g     generate diffs of the selected patch sets

       -s <patchset>[-[<patchset>]][,<patchset>...]
              generate  a diff for a given patchsets and patchset
              ranges

       -a <author>
              restrict output to patchsets created by author

       -f <file>
              restrict output to patchsets involving file

       -d <date1> -d <date2>
              if just one date specified,  show  revisions  newer
              than date1.  If two dates specified, show revisions
              between two dates.

       -l <regex>
              restrict output to patchsets matching regex in  log
              message

       -b <branch>

       -t     show some brief memory usage statistics

       --norc when invoking cvs, ignore the .cvsrc file

       --summary-first
              when multiple patchset diffs are  being  generated,
              put  the  patchset summary for all patchsets at the
              beginning of the output.

       --test-log <captured cvs log file>
              for testing changes, you can capture cvs  log  out­
              put,  then  test against this captured file instead
              of hammering some poor CVS server

       --bkcvs
              (see note below) for use  in  parsing  the  BK->CVS
              tree  log  formats  only.   This enables some hacks
              which are not generally applicable.

       --no-rlog
              disable the use of rlog internally.  Note: rlog  is
              required  for  stable PatchSet numbering.  Use with
              care.

       --diffs-opts <option string>
              send a custom set of options to diff,  for  example
              to  increase the number of context lines, or change
              the diff format.

       --cvs-direct (--no-cvs-direct)
              enable (disable) built-in  cvs  client  code.  This
              enables  the 'pipelining' of multiple requests over
              a single client, reducing the overhead of handshak­
              ing  and authentication to one per PatchSet instead
              of one per file.

       --debuglvl <bitmask>
              enable various debug output channels.

       -Z <compression>
              A value 1-9 which specifies amount of  compression.
              A value of 0 disables compression.

       --root <cvsroot>
              Override  the setting of CVSROOT (overrides working
              dir. and environment)

       -q     Be quiet about warnings.

       <repository>
              Operate  on  the  specified  repository  (overrides

       one where there are patchsets  which  are  chronologically
       (and  thus  by  patchset id) earlier than the tag, but are
       tagwise after.  These tags will be marked  as  '**FUNKY**'
       in the Tag: section of the cvsps output.  When a funky tag
       is specified as one of the '-r' arguments, there are  some
       number  of  patchsets  which  need to be considered out of
       sequence.  In this case, the patchsets themselves will  be
       labeled FUNKY and will be processed correctly.

       The  second is called an INVALID tag.  An invalid tag is a
       tag where there are patchsets  which  are  chronologically
       (and  thus by patchset id) earlier than the tag, but which
       have members which are tagwise both before, and after  the
       tag, in the same patchset.  If an INVALID tag is specified
       as one of the '-r' arguments, cvsps will flag each  member
       of  the  affected patchsets as before or after the tag and
       the patchset  summary  will  indicate  which  members  are
       which, and diffs will be generated accordingly.


NOTE ON CVS VERSIONS

       Among  the  different cvs subcommands used by cvsps is the
       'rlog' command.  The rlog command is used to get  revision
       history of a module, and it disregards the current working
       directory.  The important difference  between  'rlog'  and
       'log'  (from cvsps perspective) is the 'rlog' will include
       log data for files not in the current  working  directory.
       The  impact  of  this is mainly when there are directories
       which at one time had files, but are now empty,  and  have
       been  pruned  from  the  working  directory  with the '-P'
       option.  If 'rlog' is not used, these files logs will  not
       be parsed, and the PatchSet numbering will be unstable.

       The  main  problem  with 'rlog' is that, until cvs version
       1.11.1, 'rlog' was an alias for the 'log'  command.   This
       means,  for  old  versions  of  cvs,  'rlog' has different
       semantics and usage.  cvsps will attempt  to  work  around
       this  problem by detecting capable versions of cvs.  If an
       old version is detected, 'log' will  be  used  instead  of
       'rlog', and YMMV.


NOTE ON GENERATED DIFFS

       Another  important  note is that cvsps will attempt, when­
       ever possible, to use the r-commands (rlog, rdiff  and co)
       instead  of  the  local  commands (log, diff, and update).
       This is to allow cvsps to function  without  a  completely
       checked  out tree.  Because these r-commands are used, the
       generated diffs will include the module directory in them,
       and  it is recommended to apply them in the working direc­
       tory with the -p1 option to the patch  command.   However,
       if  the  --diff-opts  option  is specified (to change, for
       example, the lines of context), then rdiff cannot be used,
       because  it  doesn't  support  arbitrary options.  In this
       when -u and -x options are used).


NOTE ON CVS-DIRECT

       As  of version 2.0b6 cvsps has a partial implementation of
       the cvs client code built in.  This reduces the RTT and/or
       handshaking  overhead  from one per patchset member to one
       per patchset.  This dramatically increases  the  speed  of
       generating  diffs  over a slow link, and improves the con­
       sistency of operation.  Currently the --cvs-direct  option
       turns  on  the  use  of this code, but it very well may be
       default by the time 2.0 comes out.  The built-in cvs  code
       attempts to be compatible with cvs, but may have problems,
       which should be  reported.   It  honors  the  CVS_RSH  and
       CVS_SERVER  environment  variables, but does not parse the
       ~/.cvsrc file.


NOTE ON CVSPS RC FILE

       CVSps parses an rc file at startup.  This file  should  be
       located  in  ~/.cvsps/cvspsrc.   The  file  should contain
       arguments, in the exact syntax as the  command  line,  one
       per line.  If an argument takes a parameter, the parameter
       should be on the same line as the argument.


NOTE ON DATE FORMATS

       Dates have formats.  Fixme.


SEE ALSO

       cvs(1), ci(1), co(1), cvs(5), cvsbug(8), diff(1), grep(1),
       patch(1), rcs(1), rcsdiff(1), rcsmerge(1), rlog(1).


REPORTING BUGS

       Report bugs to "David Mansfield <cvsps@dm.cobite.com>"


BUGS

       No known bugs.

                                                         cvsps(1)

An undefined database error occurred. SELECT distinct pages.pagepath,pages.pageid FROM pages, page2command WHERE pages.pageid = page2command.pageid AND commandid =


  
Help us cut cost by not downloading the whole site!
Use of automated download sofware ("harvesters") such as wget, httrack, etc. causes the site to quickly exceed its bandwidth limitation and therefore is expressedly prohibited. For more details on this, take a look here

Login
Nickname

Password

Security Code
Security Code
Type Security Code


Don't have an account yet? You can create one. As a registered user you have some advantages like theme manager, comments configuration and post comments with your name.

Help if you can!


Amazon Wish List

Did You Know?
You can choose larger fonts by selecting a different themes.


Friends



Tell a Friend About Us

Bookmark and Share



Web site powered by PHP-Nuke

Is this information useful? At the very least you can help by spreading the word to your favorite newsgroups, mailing lists and forums.
All logos and trademarks in this site are property of their respective owner. The comments are property of their posters. Articles are the property of their respective owners. Unless otherwise stated in the body of the article, article content (C) 1994-2013 by James Mohr. All rights reserved. The stylized page/paper, as well as the terms "The Linux Tutorial", "The Linux Server Tutorial", "The Linux Knowledge Base and Tutorial" and "The place where you learn Linux" are service marks of James Mohr. All rights reserved.
The Linux Knowledge Base and Tutorial may contain links to sites on the Internet, which are owned and operated by third parties. The Linux Tutorial is not responsible for the content of any such third-party site. By viewing/utilizing this web site, you have agreed to our disclaimer, terms of use and privacy policy. Use of automated download software ("harvesters") such as wget, httrack, etc. causes the site to quickly exceed its bandwidth limitation and are therefore expressly prohibited. For more details on this, take a look here

PHP-Nuke Copyright © 2004 by Francisco Burzi. This is free software, and you may redistribute it under the GPL. PHP-Nuke comes with absolutely no warranty, for details, see the license.
Page Generation: 0.04 Seconds