Jimmie Mayfield wrote:
> I agree wholehartedly with the backup concept. The way I implement it
> is through a rudimentary sort of version control: I begin a project in
> a v0.1 directory. After each significant change change to my code
> (whether it's a fdesign change or otherwise), I increment the
> version number, create a new directory and copy my files over. The
> new directory becomes my work directory and the old directory is
> tarred and gzipped. This way I have a complete history of my code
> development in the event I want to see when a particular problem appeared
> and I don't have to go through the trouble of setting up a sccs system.
Uff!
To manage all the directories 'by hand' is IMHO a big overhead. I'd
have about 25 directories *per form* now! The data is very redundant.
I suggest you should try RCS for version control. It's much easier
then SCCS and - in addition - GNU make can automatically handle
those versions.
You just type
"ci file.c file.h file.fd ..."
to check in the named files in an archive. To check them out, you
similarly type
"co -l file.c file.h file.fd ..."
An optional parameter is provided to specify a version of a file.
That's all I do with version control. It's fairly simple and easy
to use.
Frank.
---------------------------------------------------------------
_/_/_/_/ _/_/ _/_/_/ EAD-Systeme GmbH
_/ _/ _/ _/ _/ Nachfeldstr. 4
_/_/_/ _/ _/ _/ _/ D-82490 Farchant, Germany
_/ _/_/_/_/_/ _/ _/ Phone: +49 8821 9623-0
_/_/_/_/ _/ _/ _/_/_/_/ Fax: +49 8821 9623-20
---------------------------------------------------------------
Email: EAD-Frank.Stefani@t-online.de
---------------------------------------------------------------
_________________________________________________
To unsubscribe, send the message "unsubscribe" to
xforms-request@bob.usuf2.usuhs.mil or see
http://bob.usuf2.usuhs.mil/mailserv/xforms.html
Xforms Home Page: http://bragg.phys.uwm.edu/xforms
List Archive: http://bob.usuf2.usuhs.mil/mailserv/list-archives/