Since we are so early in the game, I'm not sure if it really matters whether
we keep the version information or not. Does anyone have a problem with me
deleting the header files and readding them under include/parrot/. or is the
general concensus moving the RCS files?
Also, would anyone like to see a standard C comment header that includes the
RCS information added to each file?
Thanks!
Tanton
-----Original Message-----
From: Robert Spier
To: [EMAIL PROTECTED]
Sent: 9/14/2001 3:11 PM
Subject: RE: Half-completed parrot/parrot.h conversion?
Quoting Dan Sugalski <[EMAIL PROTECTED]>:
> Hmmm. I think we need a reorg of the source directories, then. I'll
get
>
> with Simon and coordinate doing this. (It's going to make CVS *so*
> happy... :)
It's often easier to do this by moving the RCS files inside the CVS
respository
directly - it's cleaner because you keep the per-file versioning
information,
which is more important than the location information which gets lost.
Otherwise you end up with a "delete this file" and recreate it elsewhere
as r1.1.
-R
