I still have the same problem outlined in this message posted last week
with the latest stable source of cvs, version 1.11.15:
fdtdb3d(KSH)> $HOME/tmpwork/cvs-1.11.15/bin/cvs -d $HOME/gfdtssrc1 history -p
gfdtsadm -c request
M 2004-02-18 16:46 +0000 fdtssrc 1.2 request evserver/pkg
== ~/tmpwork/wc/MAIN/evserver
M 2004-02-18 19:20 +0000 fdtssrc 1.2 LocalRules gfdtsadm
== ~/tmpwork/wc/MAIN/gfdtsadm
M 2004-02-18 19:20 +0000 fdtssrc 1.2 gfdtsadm.env gfdtsadm
== ~/tmpwork/wc/MAIN/gfdtsadm
M 2004-02-18 19:20 +0000 fdtssrc 1.4 prepareDelivery.sh gfdtsadm
== ~/tmpwork/wc/MAIN/gfdtsadm
A 2004-01-12 18:50 +0000 fdtssrc 1.1 release gfdtsadm/CVSADMIN
== ~/tmpwork/wc/gfdtssrc1/gfdtsadm/CVSADMIN
M 2004-02-18 19:20 +0000 fdtssrc 1.7 release gfdtsadm/CVSADMIN
== ~/tmpwork/wc/MAIN/gfdtsadm
M 2004-05-05 14:09 +0000 fdtssrc 1.18 release gfdtsadm/CVSADMIN
== ~/tmpwork/wc/MAIN/gfdtsadm
M 2004-02-18 19:20 +0000 fdtssrc 1.2 app.LN.cf gfdtsadm/etc
== ~/tmpwork/wc/MAIN/gfdtsadm
M 2004-05-05 14:09 +0000 fdtssrc 1.5 app.LN.cf gfdtsadm/etc
== ~/tmpwork/wc/MAIN/gfdtsadm
M 2004-02-18 19:20 +0000 fdtssrc 1.2 app.NY.cf gfdtsadm/etc
== ~/tmpwork/wc/MAIN/gfdtsadm
M 2004-05-05 14:09 +0000 fdtssrc 1.5 app.NY.cf gfdtsadm/etc
== ~/tmpwork/wc/MAIN/gfdtsadm
M 2004-02-18 19:20 +0000 fdtssrc 1.2 app.TK.cf gfdtsadm/etc
== ~/tmpwork/wc/MAIN/gfdtsadm
M 2004-05-05 14:09 +0000 fdtssrc 1.5 app.TK.cf gfdtsadm/etc
== ~/tmpwork/wc/MAIN/gfdtsadm
M 2004-02-18 19:20 +0000 fdtssrc 1.2 app.cf gfdtsadm/etc
== ~/tmpwork/wc/MAIN/gfdtsadm
M 2004-05-05 14:09 +0000 fdtssrc 1.4 app.cf gfdtsadm/etc
== ~/tmpwork/wc/MAIN/gfdtsadm
A 2004-02-18 19:20 +0000 fdtssrc 1.2 interfaces.dev.Solaris.txt gfdtsadm/etc
== ~/tmpwork/wc/MAIN/gfdtsadm
A 2004-02-18 19:20 +0000 fdtssrc 1.2 interfaces.prod.Solaris.txt gfdtsadm/etc
== ~/tmpwork/wc/MAIN/gfdtsadm
M 2004-02-18 19:20 +0000 fdtssrc 1.2 makefile gfdtsadm/etc
== ~/tmpwork/wc/MAIN/gfdtsadm
M 2004-02-18 19:20 +0000 fdtssrc 1.2 start_services.LN.cf gfdtsadm/etc
== ~/tmpwork/wc/MAIN/gfdtsadm
M 2004-02-18 19:20 +0000 fdtssrc 1.2 start_services.NY.cf gfdtsadm/etc
== ~/tmpwork/wc/MAIN/gfdtsadm
M 2004-02-18 19:20 +0000 fdtssrc 1.2 stop_services.LN.cf gfdtsadm/etc
== ~/tmpwork/wc/MAIN/gfdtsadm
M 2004-02-18 19:20 +0000 fdtssrc 1.2 stop_services.NY.cf gfdtsadm/etc
== ~/tmpwork/wc/MAIN/gfdtsadm
M 2004-02-18 19:20 +0000 fdtssrc 1.2 Makefile gfdtsadm/pkg
== ~/tmpwork/wc/MAIN/gfdtsadm
M 2004-02-18 19:20 +0000 fdtssrc 1.2 postinstall gfdtsadm/pkg
== ~/tmpwork/wc/MAIN/gfdtsadm
M 2004-02-18 19:20 +0000 fdtssrc 1.3 prototype gfdtsadm/pkg
== ~/tmpwork/wc/MAIN/gfdtsadm
M 2004-02-18 19:20 +0000 fdtssrc 1.2 request gfdtsadm/pkg
== ~/tmpwork/wc/MAIN/gfdtsadm
M 2004-02-18 20:28 +0000 fdtssrc 1.2 request gfdtsdb/pkg
== ~/tmpwork/wc/MAIN/gfdtsdb
A 2004-02-18 20:28 +0000 fdtssrc 1.2 tap_request_tbl.sql
gfdtsdb/reference/tbl == ~/tmpwork/wc/MAIN/gfdtsdb
/opt/fdtssrc/tmpwork/wc/MAIN/gfdtsadm/pkg
Natarajan Murugaiyan(Ravi)
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
Behalf Of Murugaiyan, Natarajan [IT]
Sent: Friday, April 30, 2004 9:38 AM
To: [EMAIL PROTECTED]
Subject: cvs history command
I have trouble getting the 'cvs history' command to work.
When I run the 'cvs history -p gfdtsadm -c request' command, hoping to get
all commits by anyone for the file 'request' in module 'gfdtsadm', I get 23 records
and none of them are for the file 'request'.
The 23 matching records are for files other than 'request' in module 'gfdtsadm'
and other files in other modules in the same source tree.
I am accessing the repository using cvs client 1.10 from a solaris 2.6 box
accessing the repository running on a solaris 2.8 box.
On the server, the CVS/history file in the source tree has some records for the
'request' file of 'gfdtsadm' module:
$ grep request history | grep gfdtsadm
M401859a2|sz84534|<remote>|gfdtsadm/pkg|1.1.1.1.2.1|request
M4027bd56|sz84534|<remote>|gfdtsadm/pkg|1.1.1.1.2.2|request
M40310062|sz84534|<remote>|gfdtsadm/pkg|1.1.1.1.2.3|request
M403286c1|vk84407|<remote>|gfdtsadm/pkg|1.1.1.1.2.4|request
M4033baf7|fdtssrc|~/tmpwork/wc/MAIN/gfdtsadm|gfdtsadm/pkg|1.2|request
M403e7fbe|nm79568|<remote>|gfdtsadm/pkg|1.3|request
G4045f218|nm79568|<remote>*8|gfdtsadm/pkg|1.3|request
M4045f7ea|nm79568|<remote>|gfdtsadm/pkg|1.4|request
M40522c77|nm79568|<remote>|gfdtsadm/pkg|1.5|request
The CVSROOT/config file of the source tree has no 'LogHistory' keyword specified in it
implying
the default log level for history file.
I have tried following variations of the history command but none of them give the
info I am looking for:
cvs history -w -p gfdtsadm -c request
cvs history -p gfdtsadm -c pkg/request
cvs history -p gdftsadm -c gfdtsadm/pkg/request
cvs history -m gfdtsadm -c request
cvs history -n gfdtsadm -c request
Does anyone know what is the difference between the -m, -p and -n options for the 'cvs
history' command?
Natarajan Murugaiyan(Ravi)
_______________________________________________
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
_______________________________________________
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
