Hi,There are many commits theses days, for latex pres, for rebsqlite, elsedetect, images …
And *all* commits log don't speak about what and why the commit exist. Could you please make commit :
o Which have a tag or something to see what it concern, like "oral pres:" or "annal speech:" or "rebsqlite: " or whatever, I don't care, but it unriable to see which commit concern which part of the projet
o Which have a description of the evolution, like "This add a function whatever_fun() which all us to make a scrot, so …" (And … is the suit, not for the commit log) or "Create toto.tex file which will be used for …"
For both 2 bottom point, have a look to what is done on Kernel Git, X.org Git, and simply any SCM (sourceforge projects, gna …)
o Which have been tested. Many commits are for typos correction (I don't say that for grammar, but for syntax, variables names …) and are not good in a QA prespective.
o Which have correct english, not franglish word. It doesn't take so many time to make our head work a bit. And it will also make improve our english (and for devel list too). Also http://translate.google.com/translate_t exist.
It's too crap for now, it make no sense, it's unriable. Also.As we remind yesterday, we have a coding normalizes, will it be possible to follow it ?
We also already have a directory arboresence, why mix all and make search and find file *fast* (or simply find them) impossible ? And that's also true for files which have date in them. Think performance and reability.
A lot ot things make no sense, it's horrible. My 2 cents. -- Beber -- Email / Jabber (+GMail) : beber^^meleeweb.net http://www.meleeweb.net
pgpptN2k8ECXc.pgp
Description: Signature numérique PGP
