[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: Thu, 16 Aug 2007 08:56:17 -0500
User-agent: Thunderbird (X11/20070716)

Hans Schwaebli wrote, On 08/16/2007 07:42 AM:
I must be talking Chinese.

No, I believe we actually understood you in the message you sent
Wed, 15 Aug 2007 07:14:52 -0700 (PDT). The problem is that we apparently are using language that you do not understand, even though I thought that I was pointing out how to DO what needed done and where to learn the language.

I even tried to give you commands that would do what you need done (in the bash scripting language, for the Unix command line).

But until you understand that physically destroying your sandbox, destroys part of CVS's ability to do what you NEED, we will not be able to help you further. Maybe we are getting stuck on this point, but you are not helping us understand that you now understand not to use the OS to remove a version controlled directory.

Two last suggestions:
1) Read all of the following links and then re read the emails you have been 
2) try your luck getting answers on the CVSNT list, you may be needing the response sent back to you in windows-ese.

good luck.

"Denniston, Todd A CIV NAVSURFWARCENDIV Crane, Code 6067" <address@hidden> 
  Hans Schwaebli wrote, On 08/15/2007 09:14 AM:
Am I misunderstanding you or are you misunderstanding me?
Please try to get out of your CVS implementation thinking and open your mind to 
There is a directory with subdirectories and files which has been previously checked in.
{rearrange block}
Assume I DON'T know what has been changed in this directory, or if anything at all has been changed. My skript runs at night, automatically and unattended. It is stupid. It does not know what has been changed.
It needs an education, it (according to your requirements below) is required to learn a few things.

Assume either you can do this under Unix, Cygwin or get working tools for 
Now imagine some random changes afterwards in this directory like:
- subdirectories have been added
d1 now contains new directory

cd d1
if ! grep new CVS/Entries >> /dev/null
cvs add new

- some subdirectories have been deleted, which have been previously checked in
your process now needs to have folks/programs run `cvs remove -f file` only, and let .cvsrc and `cvs update` take care of deleting subdirectories.
- some files have been modified
the cvs commit at the end should take care of that if you did not blow away the CVS control directory.
- some files have been added
cd d1
if ! grep filename CVS/Entries >> /dev/null
#Hope you never have binary files or compile products just laying about.
cvs add filename

- some files have been deleted, which have been previously checked in
if they were deleted with `cvs remove -f file` then they will be cleaned up with a `cvs commit`.

The requirement is that this nightly script commits every change in this directory, unattended, automatically, by force if there are any conflicts. Thats the
How do I solve this with CVS?
What do you mean with "and the 'cvs checkout' commands into your .cvsrc"? I 
don't understand how this can help me for my question. Or any other answer you gave me.
If it does not work with CVS, just say so, PLEASE, so that I understand it 

Todd Denniston
Crane Division, Naval Surface Warfare Center (NSWC Crane)
Harnessing the Power of Technology for the Warfighter

reply via email to

[Prev in Thread] Current Thread [Next in Thread]