On Mon, Sep 22, 2003 at 02:37:08PM -0400, Tom Copeland wrote: > On Mon, 2003-09-22 at 12:42, [EMAIL PROTECTED] wrote: > > All; > > We seem to have two different styles to working with CVS here and > > I want to know what the standard is in the community. > > > > One group says that you never ever change your working area. You > > just do updates and keep working on. > > That's what I do. > > > The other group says you should change your working area and start > > with a fresh checkout. I agree with the second group. I like the > > idea of always starting a task with a fresh clean checkout. I think > > work areas should be temporary and be deleted when you are done with a > > task. > > Hm. That's interesting. Why do you feel the work area should be > temporary?
I like the temporary work area because it is always up to date without having to do a cvs update -d -p or in wincvs using the update command and checking the options. I also know that a checkout will create all directories and files. Where with wincvs we run into issues where it seems like some directories are skipped. I also like starting with the new area because it prevents having those non-cvs files that I don't need any more or that where created as part of the compile process. I also find I have to answer more questions of the type, why didn't my file get up-dated? Why am I getting the error message: "file.c is in the way and needs to be moved"? I know a lot of this training, but it seems like some people never get it. I also find that people are more careful about making sure they have committed all of their files that are needed in a build to cvs when they remove their old work area. This just makes my job so much easier. I get a lot less hourly/daily build failures when this policy is in force. Joseph _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
