🚀 go-pugleaf

Ed Beroset <beroset@mindspring.com> wrote in message news:<XpfKc.1545$iK.141@newsread2.news.atl.earthlink.net>...
> Peter wrote:
> > Hi
> >    Would you like to tell me your company's "source code backup
> > procedure"?
> > 
> > Here is mine:
> > 1)	Any source code, document or other material that modified, should
> > be backup end of each day.
> > 2)	All the backup material should store in
> > \\cadence-pdf\backup\<project name>\<yyyymmdd>
> > 3)	For security reason, all the backup material should be zipped with
> > a password.
> > 4)	All the document should include a version number and last modified
> > date.
> 
> What I do is to use a source code control package (CVS is free, for 
> example) and then back up that, just like any other valuable computer 
> data.  You sound like you're mixing source code control with backups. 
> They're separate concepts.
> 
> Ed

Thanks for you reply
   I mean source code backup , not source code version control. Does
your company have some specific procedure of doing that?

thanks
from Peter