Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Hi, I am new to CVS and hava some questions want to ask.
After I add all project files and binary to CVS and when I build a new .exe file. How can I know which project file(s) have been modify on this newly build? I know I can record them down by hand, but do CVS has a function that keep track which files have been modify under a specific build??
oh, I know "cvs history" is the command that I want. but after I commit some files, then type "cvs history", nothing show up....
do I type the command wrong?
(from cvs man-file)
history
Show reports on cvs commands that you or others
have executed on a particular file or directory in
the source repository. (Does not change repository
or working directory.) History logs are kept only
if enabled by creation of the `$CVSROOT/CVS-
ROOT/history' file; see cvs(5).
Logging must be enabled by creating the file `$CVSROOT/CVSROOT/history'.
I think you must check in that file as an admin of cvs not 100% sure though. CVS can keep a history file that tracks each use of the checkout, commit, rtag, update, and release commands.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.