info-cvs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Question about convenient and automated committing


From: Hans Schwaebli
Subject: Re: Question about convenient and automated committing
Date: Thu, 16 Aug 2007 05:42:32 -0700 (PDT)

I must be talking Chinese.
 


"Denniston, Todd A CIV NAVSURFWARCENDIV Crane, Code 6067" <address@hidden> wrote:
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 this:
> 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 windows.
> 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
then
cvs add new
fi

> - some subdirectories have been deleted, which have been previously checked in

http://cvsnt.org/manual/html/Removing-directories.html
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
then
#Hope you never have binary files or compile products just laying about.
cvs add filename
fi


> - 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
requirement.
> 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 clearly.
>
>


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


Fussy? Opinionated? Impossible to please? Perfect. Join Yahoo!'s user panel and lay it on us.
reply via email to

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