Re: [RFC] CVS directory structure

> I don't see why using the CVS-checkout-dir for development is bad. > I'm doing it myself this way, many others do also, many tools do it > this way (as Tobi has already mentioned on the list). You simply work > in your source and when all files have been modified e.g. to contain > a new function you simply check in that directory-tree. This way you > are sure that you will check in all files that you modified and can > asure that everything that's in CVS will function as you tested it > locally. > The way Bertrand (I think it was him - but that's not too important > here) proposed seems a bit strange to me. Why should I do a checkout > from CVS to the local disk, copy those files again somewhere, do > modifications to e.g. 5 files and be sure to copy all 5 files back to > check them in? If I see I'm stuck with the modifications I've done to > those 5 files I can simply remove them, do a "cvs update" and have > all my correct working-files I had before the "experiment". What's > bad about it? Well, if you copy all the files back and run a cvs diff you'll see what has changed :) anyway, i agree the current structure makes it weird to develop with sometimes but it's nothing that cannot be done. Arnaud.