| |
|
 |
Version Control management with CVS - Part 2
|
Conclusion
You should now have the knowledge to perform changes to projects, whether good or bad, with the use of CVS. You should also know how to create patches in case you just have anonymous read access. So why not help out your favorite Open Source project and make the world a better place.
The next part in this series will go into the details of CVS repository management, that is creating a new CVS repository, importing sources and handling CVS modules. For those of you who simply cannot wait I recommend you either check out the man pages for CVS, read it's PostScript version (usually located in /usr/doc/), the online manual or the PDF document
Any comments on how to improve this article or future parts is very welcome.
Comment List
| Topic: |
Author: |
Time: |
|
regexps are supported
|
Marius Sundbakken
|
26.11.2000 05:23
|
|
When commiting changes, it is often necessary to commit both the header file and the source file, and conveniently, cvs support:
cvs commit foobar.*
|
|
RE: regexps are supported
|
Jan Ekholm
|
27.11.2000 10:57
|
|
> When commiting changes, it is often necessary to commit both the header file and the source file, and conveniently, cvs support:
>
> cvs commit foobar.*
Isn't this expanded by the shell? CVS just gets the expanded list, such as:
cvs commit foobar.h foobar.cpp
Or am I out in thw woods here?
|
|
RE: RE: regexps are supported
|
Michael Krumpus
|
27.11.2000 15:40
|
|
> > When commiting changes, it is often necessary to commit both the header file and the source file, and conveniently, cvs support:
> >
> > cvs commit foobar.*
>
> Isn't this expanded by the shell? CVS just gets the expanded list, such as:
>
> cvs commit foobar.h foobar.cpp
>
> Or am I out in thw woods here?
You are correct. The shell handles this, not CVS (or any other program).
|
|
 |
|
|