-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Neil Conway wrote:
| Derek Price wrote:
|
| You're welcome. I'm looking forward to seeing a patch!
|
|
| Ok, I finally had a chance to look this at. Below is a WIP patch.
| Example output:
|
| [neilc:/home/neilc/cvs_test]% ~/cvs-1.12.11/src/cvs log
Derek Price wrote:
You're welcome. I'm looking forward to seeing a patch!
Ok, I finally had a chance to look this at. Below is a WIP patch.
Example output:
[neilc:/home/neilc/cvs_test]% ~/cvs-1.12.11/src/cvs log aaa.c
[...]
revision 1.4
date: 2005-03-10 14:57:28 +1100; author: neilc; state:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Neil Conway wrote:
| Derek Price wrote:
|
| You will need to count the total number of lines in the HEAD
| revision and keep it up to date as added and deleted lines for
| other revisions are processed. Later, in `cvs log', these new
| fields should be
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Neil Conway wrote:
| On Tue, 2005-02-15 at 12:41 +1100, Neil Conway wrote:
|
| I would like to see lines: +3 0 associated with revision 1.1.
| It is possible to get the number of lines modified via a kludge
| (fetch the 1.1 revision of the file and
Derek Price wrote:
You will need to count the total number of lines in the HEAD revision
and keep it up to date as added and deleted lines for other revisions
are processed. Later, in `cvs log', these new fields should be usable
in conjunction with added and removed lines to get the output you are
On Tue, 2005-02-15 at 12:41 +1100, Neil Conway wrote:
I would like to see lines: +3 0 associated with revision 1.1. It is
possible to get the number of lines modified via a kludge (fetch the 1.1
revision of the file and manually count the number of lines in it), but
I think it would be
CVS does not record the number of lines in a newly-added file. For
example:
% cat newfile.c
line 1
line 2
line 3
% cvs add newfile.c
cvs add: use `cvs commit' to add this file permanently
% cvs ci -m File added. newfile.c
/var/lib/cvs/cvs_test/newfile.c,v -- newfile.c
initial revision: 1.1
%
