Ok,
I'll fix it to where all header files are in a separate parrot subdirectory.
-----Original Message-----
From: Dan Sugalski
To: Gibbs Tanton - tgibbs
Cc: [EMAIL PROTECTED]
Sent: 9/14/2001 12:36 PM
Subject: RE: Half-completed parrot/parrot.h conversion?

At 01:03 PM 9/14/2001 -0400, Gregor N. Purdy wrote:
>Gibbs --
>
> > The patch assumes that your source code directory is named parrot.
> > This may
> > have been an invalid assumption, but it is going to be hard to do
this 
> patch
> > unless we agree on the name of the source directory.
>
>Ah. I try not to assume the source directory name, since folks might
>rename it for various reasons (for instance, I always check out CVS
>code as foo-cvs rather than just foo to call my attention to it in
>its parent directory).

I think that, if we're going to put the includes in the parrot subdir, 
there should be a parrot/ under the CVS root dir. Whether we put all the

source there or not's a separate problem.

                                        Dan

--------------------------------------"it's like
this"-------------------
Dan Sugalski                          even samurai
[EMAIL PROTECTED]                         have teddy bears and even
                                      teddy bears get drunk

Reply via email to