Re: Question about convenient and automated committing

[Hans Schwaebli]

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. Now imagine some random changes afterwards in this directory like:
- subdirectories have been added
- some subdirectories have been deleted, which have been previously checked in
- some files have been modified
- some files have been added
- some files have been deleted, which have been previously checked in

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.

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.


Spiro Trikaliotis <address@hidden> wrote:

> Hello Hans,
>
> * On Wed, Aug 15, 2007 at 01:50:15AM -0700 Hans Schwaebli wrote:
> > 
> > 1. I want to commint ANY changes inside a folder
>
> This is what "cvs commit" (or "cvs ci", the synonym) does. At least, it
> commits ANY changes CVS even cares about.
>
> > (yes, they do exist in the IT world since very long times), which
> > means subfolders, files and so on. Any changes means any
> > modifications, including
>  deletions of files and folders inside this
> > folder.
>
> CVS (and, btw, Subversion, too) does not care at all about folders.
> Thery are just present if they were generated at any time back in
> history.
>
> > CVS does not know anything of folders? Nevertheless I ask for a
> > solution how to commit every change in this folder, any change in all
> > files and subfolders. Does it work with CVS, yes or no, and if yes,
> > how?
>
> Again: "cvs commit" is what you are asking for.
>
> Any, you might want to add the -P command for the "cvs update" and the
> "cvs checkout" commands into your .cvsrc. This way, CVS will not show
> empty directories when doing an update or a checkout. Note, however,
> that this option gets tricky when doing branches (with "cvs tag"). In
> this case, I suggest using "cvs rtag".
>
> Additionally, this option is tricky when you want to "recreate" a
> directory that was once empty.
>
> But you already know
>  most of this, Larry already explained it. This is
> the only way to work with CVS here, as it is the way CVS works.
>
> The only other options I see are:
>
> 1. Check out if meta-cvs (or other tools on top of CVS) support
> directories (I do not know, you have to check yourself).
>
> 2. If the directory is realy, really, REALLY not needed anymore, you
> might consider deleting it from the repository (that is, from the
> server). Note that you loose anything that was once inside that;
> thus, I do not recommend this unless the directory was created by
> accident only.
>
> HTH,
> Spiro.
>
> -- 
> Spiro R. Trikaliotis http://opencbm.sf.net/
> http://www.trikaliotis.net/ http://www.viceteam.org/

---

Got a little couch potato? 
Check out fun summer activities for kids.

---

Boardwalk for $500? In 2007? Ha! 
Play Monopoly Here and Now (it's updated for today's economy) at Yahoo! Games.