time to check in?

[Ben Pfaff]

I'm beginning to wonder whether it would be better to check in
the set of changes we have now.  It has changed from being a
brief "reorganization" to a major code cleanup.  That's not
necessarily a bad thing, but it means that it becomes more
difficult to coordinate.  CVS isn't perfect but it does make it
easier to coordinate changes.

We don't have to get the file names perfect yet.  As long as a
ChangeLog exists to explain what's been done (I assume you'll be
adding your own ChangeLog entries before you check in), we can
figure out what happened over a series of renames.

Also I worry about becoming less transparent to outsiders.
Anyone who looks at the CVS tree at the moment will think nothing
much is going on.  That's certainly not true.

I dunno.  What do you guys think?

-- 
"The fact is, technical people are better off not looking at patents. If
 you don't know what they cover and where they are, you won't be knowingly
 infringing on them. If somebody sues you, you change the algorithm or you
 just hire a hit-man to whack the stupid git." --Linus Torvalds