[EMAIL PROTECTED] on 2000.02.21 11:34:52 >Noel Yap wrote: > >> Beware of premature optimisation. We've already laid out a process that >> relies >> on empty directories being created in the repo. IOW, it's *necessary* to >> allow >> creation of empty directories for this process. It would be a kludge to >> create >> a dummy file for this purpose. > [smc] (ok I'm repeating myself..sorry.) But if you ever decide to > use branches Noel, this "kludge" is exactly what you will have to > do. And branches are such a major part of CVS, you shouldn't just > ignore them just because you don't happen to use them. > > Because of the way that CVS decides if directories are > present or absent on a branch (by checking if there are any files > within the directory (or subdirs) that are present on the branch) > this means it isn't possible to "fix" it without introducing >something > extra to keep track of directories...which I'm not sure is a good > idea. (and I bet there is at least one person who thinks it is a > _terrible_ idea :-) I'd rather see the trunk behave consistently > with how branches behave...that is: No empty directories. This is fine, so long as the consistency is done by "cvs co", "cvs export", and "cvs up". It should not be done via "cvs add" or "cvs ci". Noel
