[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Errors and missing information in node "loginfo" in

From: Jakub Narebski
Subject: Errors and missing information in node "loginfo" in
Date: Fri, 29 Jun 2001 16:30:08 +0200 (CEST)

Concurrent Versions System (CVS) 1.11 (client/server)

The information about expanding format string in loginfo is wrong.
The details are below (at the end of this file).

There is no information about format of input to command specified in
loginfo file. As far as I tested this format is different for imports
and for commits.

For both commit and import the first two lines are the following
(the output is indented for better readibility; to get actual input one
has to remove two leading spaces).

  Update of $CVSROOT/$subdirectory
  In directory $host:$working_copy_directory

Next part is different for import and commit. For import there is "Log
Message:" section and _next_ comes info about import, in particular about
imported files. For commit _first_ is informationa about
added/removed/modified files, and next the log message. I really wonder

For commits there comes line with the current operation/operations, namely
"Added Files:", "Removed Files:" or "Modified Files:". In the next line
(or lines; because this is not documented I'm not sure) there is, indented
with TAB, space separated list of added, removed or modified files. There
is no such section for added directories (because one can remove empty
directories only with checkout/update with -P option, not by commit).
There is instead "Directory $CVSROOT/$subdirectory added to repository"
log message.

For import next part (separated by empty line) is log info:

  Log Message:

This part is also after commit, but for commit it is at the very end of
input, and is _not_ separated by an empty line.

Further parts are for import solely. After log message, separated by empty
line (?) comes


I really wonder what is this section for... IIRC the cvs admin is _not_
logged via loginfo. Could anyone explain that (I know I can look into
source code for cvs, but I'm not feeling like doing it)?

Next is the information about release and vendor tag (see 'cvs import'
syntax), separated of course from log message by an empty line, namely

  Vendor Tag:   $vendor_tag
  Release Tags: $release_tag

The tags are separated from their description with TAB character.

Next, separated by an empty line, there is output of import command.
The format is

  X $module_dir/$subdir/$file

where X is one letter indicator of status. I guess that X can be C for
conflict (it can be I, for ignored), even that files with conflict and
ignored files are not put into repository (not commited).

The last line is the status of import command, e.g.

  No conflicts created by this import

The information about %{sVv} format string is also incomplete, and
what is worse _wrong_.

%V i.e. old version number (pre-checkin), can be NONE if file was added to
directory. I'm not sure if it's NONE if file was resurrected (i.e. it was
at some time present in module, removed, and now added).

%v i.e. new version number (post-checkin), can be NONE if file is being
removed from directory.

The following excerpt from about format string is *not true*
   The output will be a string of tokens separated by spaces.  For
backwards compatibility, the first token will be the repository
subdirectory.  The rest of the tokens will be comma-delimited lists of
the information requested in the format string.
In the case of import, or adding the directory, the rest of the tokens is
"- Imported sources" for import, or "- New directory" when adding the

The fact, that for each subdirectory with commited/imported files there is
_separate_ execution of command specified in loginfo is also not told (at
least not explicitely) in "loginfo" node of But one can easily
guess that...

P.S. I did not find anything about bugs in documentation in BUGS file. Is
there any list of bugs in cvs documentation? I do not know texinfo format,
so I cannot make fixes by myself, but I think that this information may

P.P.S. I would be very grateful for sending a copy of reply to
email:address@hidden, because I am not subscribed to bug-cvs nor
info-cvs list.

Jakub Narębski                      mailto:address@hidden

reply via email to

[Prev in Thread] Current Thread [Next in Thread]