[development] Move all core modules into their own directories.

Khalid B kb at 2bits.com
Sat May 20 15:15:25 UTC 2006

Just a note  on CVS implications for moving files to new locations.

There are three options that I can see:

1. Move to a better SCM (svn, bzr), where moving files becomes a non-issue.
The scope of that is huge, and has been debated to death with no concensus
and is a holy war by itself.

2. Do a cvs remove on the present file, do a cvs add on the new directory/file.
Repository integrity is maintained (checking  out old tags works), but old
history is lost.

One possible workaround is to make the first commit log message contain a
link to the attic where the old file is.

3. Move the ,v files in the repository backend. This will break old tags. For
example checking out 4.6 will not find modules/node.module, since it is
now in modules/node/node.module, and CVS knows nothing about the
old path.

Derek, you seem to be the new CVS guy around, any ideas on how to proceed
with this?

More information about the development mailing list