Hi Francesco,

ChangeLog -> CHANGES.txt
COPYING -> COPYING.txt
INSTALL -> INSTALL.txt
TODO -> TODO.txt

Why not keep ChangeLog and COPYING files for historical reasons and put inside the sentence "Please look at <new name> file" ?

About names are ok for me also if another name for ChangeLog could be UPDATES.txt, but are equivalent. I think that could be useful to add a ReadMe.1st file that inside should has (a sample):

-----------
Welcome to Harbour!
For your first look you can read:

INSTALL.txt     Installation help ....
COPYING.txt     Copyright .....
CHANGES.txt     Updates on repository
TODO.txt        to-do list ....
-----------

Well, IMO we should name these files with meaningful
names so that we don't need another file to describe
what they are. That's the reason we use these name,
because they are fairly widespread around free projects.

BTW our readme.txt has pointers to dirstruct.txt which
should have pointers to all these files, so basically
what you suggest is already implemented.

Brgds,
Viktor

_______________________________________________
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour

Reply via email to