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.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I am using cvs with my project.
When I first imported the files they got start revision 220.127.116.11
Then each commit of a new file, I get new revision for it: 1.2, 1.3 ... 1.i
No I want to declare a new version of my program: 2.0 for all files for example.
I have tried the command from the manual:
cvs commit -r3.0
but it just shows me a list of all my files in the project and does not proceed.
Any ideas which command or maybe Koqueror option would do what I need.
Thanks in Advance,
cvs commit -r 3.0 should set the revision tag to 3.0 for all files and commit them. You should be prompted with the usual editor window, listing the changed files, expecting you to add a commit comment at the bottom of the list.
It sounds like you're doing the right thing - just scroll down and add a comment - something like "Bumped all files to 3.0 release" (or whatever you want). Save the file and exit the editor and you should see the files being commited.
hw-tph, thanks for your reply.
I run that command in terminal, and when I get the list there are little options I can do, I cannot type anything, but sometimes when I press some keys it does something, I just don't know the meaning of all keys, I can check it again to be more specific if You need.
Thanks a lot,
You are most likely presented with the vi or vim editor. It takes some reading and getting used to but it's usually worth it in the long run. You do have a couple of options:
- The editor that is used for entering commit information when using cvs is controlled by a couple of environment variables, $VISUAL, $EDITOR and $CVSEDITOR. Setting any of these to the editor you would like to use would probably work, say export VISUAL="nano" (nano is a far more simple editor than vi/vim) and then do your commit.
- You could use the -m option to automatically pass the commit message, bypassing the editor step: cvs commit -r 3.0 -m "Updated all files to 3.0 release + cleanup of old references" would probably do what you want to do. I prefer doing it with the editor though, where I can see what files have changed before actually commenting on the changes. It's my personal preference and it works either way.
There are probably other ways of doing this but these are the two I came to think of right off of the top of my head. Oh, and if you want to learn vim, try typing vimtutor at the shell prompt. The vimtutor script is included with most distributions that ship with vim.