[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Question about convenient and automated committing
From: |
Todd Denniston |
Subject: |
Re: Question about convenient and automated committing |
Date: |
Wed, 15 Aug 2007 09:45:19 -0500 |
User-agent: |
Thunderbird 2.0.0.5 (X11/20070716) |
Hans Schwaebli wrote, On 08/14/2007 07:32 AM:
If I deleted some files in a folder and
I Assume you did so by using `cvs remove -f file`
I delete the same folder itself,
I Assume you did so by using `rm folder` (or a system GUI equivilent) instead
of a CVS command, seeing as there is NO cvs command to remove a directory.
what CVS command do I need to commit this change?
check it out again (because you blew away the CVS control directory before
committing),
`cvs remove -f file` on all appropriate files again,
`cvs commit -m"Those files got destroyed"`
`echo "update -Pd" >> ~/.cvsrc`
`echo "checkout -P" >> ~/.cvsrc`
cd ..
cvs update
Note, it looks like you are on windows and the above commands are for Unix, so
you will need to do an appropriate translation for the creation/modification
of your ~/.cvsrc file:
http://cvsnt.org/manual/html/cvsrc.html
"ci" does not work. I use Ant for this, so here is my example:
<cvs command="ci -R -m ${DEFAULT_CVS_COMMENT} numbers"
cvsroot="${CVSROOT}"
dest="U:/projects/HSW_TST/src/com/haefele/hsw2/tst/abstractions"/>
I see it in Eclipse that the folder is not deleted in CVS afterwards.
http://cvsnt.org/manual/html/Removing-directories.html
If you are using CVSNT on the server too, you may want to put the .cvsrc mods
above into $CVSROOT/CVSROOT/cvsrc too.
http://cvsnt.org/manual/html/cvsrc.html
Assume that I don't know the filenames which have been in that deleted folder.
I need a generic way to simply commit whatever has been changed in a directory,
no matter what kind of change it is.
Not if you already deleted the control folder (CVS) from your sandbox that
held the CVS data about that file.
http://ximbiot.com/cvs/manual/cvs-1.11.22/cvs_2.html#SEC19
Two exceptions rtag & rdiff.
For automation in the 21th century IT world
this is very important.
You expect that if you destroy random parts of your tools, then they should
continue to function at full capability? Funny, in the military we expect
that we _may_ only retain a DEGRADED capability when only _non-critical_
portions of the system are destroyed.
I hope this helped your understanding.
--
Todd Denniston
Crane Division, Naval Surface Warfare Center (NSWC Crane)
Harnessing the Power of Technology for the Warfighter
- Re: Question about convenient and automated committing, (continued)
- Re: Question about convenient and automated committing, Denniston, Todd A CIV NAVSURFWARCENDIV Crane, Code 6067, 2007/08/15
- Re: Question about convenient and automated committing, Hans Schwaebli, 2007/08/16
- Re: Question about convenient and automated committing, Todd Denniston, 2007/08/16
- Re: Question about convenient and automated committing, Garyl Erickson, 2007/08/16
- Re: Question about convenient and automated committing, Hans Schwaebli, 2007/08/17
- Re: Question about convenient and automated committing, Larry Jones, 2007/08/17
- Re: Question about convenient and automated committing, Sergei Organov, 2007/08/15
Re: Question about convenient and automated committing,
Todd Denniston <=