| |
|
 |
Version Control management with CVS - Part 2
|
Creating patches
The two previous pages explained how you can commit your changes and add files to a CVS repository if you have the proper write access. But what if you only have anonymous access and want the changes you have made locally to appear in the CVS repository?
Luckily for you there is one option and that is to create a patch and send it to someone with write access. But don't count on the changes to appear at all, it's entirely up to each developer to use the patches submitted by you. To help on this you should always send a detailed description on what you have changed and ask politely.
To create a patch you have to find out what the difference between your local copy and the CVS repository is. This is done with the CVS command diff, the usual option to use for diff is -u which outputs the difference in a unified format. You can also use the -c option which uses the context output format. So we want to do:
After a while it will start spitting out lots of text explaining the differences, to put this into a file we use redirection.
This creates a file called my.patch which can be emailed to the developer, and hopefully will be incorporated into the CVS tree.
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).
|
|
|
|
|
