[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: How to create patch for project?
From: |
Miller Dale C Contr AFWA/SDHS |
Subject: |
RE: How to create patch for project? |
Date: |
Wed, 1 Sep 2004 09:14:20 -0500 |
Mak,
The rdiff -s argument using two dates or two tags gives you good
information. It shows what files have changed, are new, or removed (in
attic) with revision numbers.
cvs -Q rdiff -s -Dyyyymmdd -Dyyyymmdd module
or
cvs -Q rdiff -s -rtag1 -rtag2 module
(I use version tags that include a date.)
Output is in the following format:
File weather/docs/index.html changed from revision 1.9 to 1.10
File weather/docs/links.htm is new; ver_20040823 revision 1.4
File weather/docs/alaska.html is removed; ver_20040524 revision 1.9
Processing this with a perl script could cvs export each file to a staging
area for transferring to another person.
This information gives you a good change list, but it does not show hacking
where files were moved, renamed, or deleted.
A find statement on the $CVSROOT/module each time you hand off an update
would document what is in the repository at the time.
find $CVSROOT/module -type f | egrep -v "Attic|CVS" | sort >module_list
Keep the snapshot under CVS. I have a module_list snapshot updated and
committed automatically (a cron job) whenever a new file is added to our
repository by touching an "add_flag" file the cron job checks for.
I actually do a find inside a perl program and then removed the ,v and the
$CVSROOT from the path. I also do not restrict it to -type f so I also have
the directory names (appending an ending slash to the directory names). The
program also commits the updated the file.
Dale Miller
Northrop Grumman Mission Systems
Bellevue, NE
>>>>> "Mak" == Mak <address@hidden> writes:
Mak> I have a situation where I cannot understand how rdiff can help me.
Mak> I'm now at a point where I now need to send him only revised files. I
Mak> need a process to checkout the project with only the files that were
Mak> changed between the last tag and now. Complete file that can be used
to
Mak> overwrite the old ones. The directory structure also need to be
Mak> maintained (naturally!!)
Mak> How would I do this? Any help is appreciated.
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- RE: How to create patch for project?,
Miller Dale C Contr AFWA/SDHS <=