---Reply to mail from David A. Desrosiers about Plucker in C (++)
> Before this gets too widespread, we should probably clean up
> that tree a bit more, add a README in that directory to provide some
> info about what it is, what license it is covered by, who wrote the
> original code, what features are present and missing, and so on.
>
> The most-important part is the license at this stage. There is
> a GPL_LICENSE.txt in that dir (which can probably be tossed, since we
> already have a COPYING file in the parent dir), and we should make
> sure that each file contains the license header as well, lest someone
> snatch one of the files before we stamp it, and use it in a way that
> violates that license.
>
> I hate to play the Warden, but we've seen abuse here before.
I guess the e-mail I send from work didn't get out.
Anyway, All done.
Don't worry about being the warden.
---End reply
Christopher R. Hawks
HAWKSoft
-------------------------------------------------------------------------
Any research done on how to efficiently use computers has been long lost
in the mad rush to upgrade systems to do things that aren't needed by
people who don't understand what they are really supposed to do with them.
-- Graham Reed, in a.s.r.
_______________________________________________
plucker-dev mailing list
[email protected]
http://lists.rubberchicken.org/mailman/listinfo/plucker-dev
