RE: Annoying "cvs commit: Examining ."

[Risman, Mark]

As Bob said, the "Examining" shows a directory which is being examined.
Here, CVS is trying to tell you that the commit command is looking at
every file in that directory. This is as opposed to what happens when
you issue a "cvs commit" with only filenames (i.e. no
directories/modules) as arguments. In the latter case, the commit will
only affect the given files, and it won't scan entire directories.

-----Original Message-----
From: address@hidden
[mailto:address@hidden On Behalf Of
Bob Proulx
Sent: Tuesday, August 25, 2009 7:24 PM
To: Jirong Hu
Cc: address@hidden
Subject: Re: Annoying "cvs commit: Examining ."

Jirong Hu wrote:
> Annoying "cvs commit: Examining ."
> This line makes me confused. What does it mean?

It is a status message describing that the command is recursively
examining the '.' directory.  The '.' directory is the current
directory and on Unix filesystems is a literal "." entry in the
current directory.  This is the default if none is supplied.

> In the following case, I run "cvs commit", then run it again. It
> gives this message but no result.

The second run has nothing to do and so doesn't print anything.

> address@hidden project1]$ cvs commit
> cvs commit: Examining .

Looking at the current directory which is the literal '.' entry.

> /cvs/projects/project1/v2_fix,v  <--  v2_fix
> new revision: 1.2; previous revision: 1.1

v2_fix is modified and so it is commited.

> address@hidden project1]$ cvs commit
> cvs commit: Examining .

Nothing to do since v2_fix is up to date.  So no action was echo
printed.

If you desire cvs to be more quiet about these status messages then
you may specify the -q option.

  cvs -q commit

Often used options may be specified on a in your ~/.cvsrc file.

Bob







**********************************************************

MLB.com: Where Baseball is Always On