On 2/6/06, Brian Mattern <[EMAIL PROTECTED]> wrote:
> the notebook API changed and examine hasn't been updated yet.

This was obvious indeed!

> I would highly recommend following CVS commits and updating when
> something is added that you want to try out rather than just blindly
> updating everything every day.

Not many people have the time (or knowledge) to follow CVS commits
every day and on top of that patching what hasn't been updated.
There's a fine line between developer and enthusiastic user who wants
to get the latest E. Of course your recommendation is good but it's
easier to update blindly once you know that a certain number of
commits have been done without going into the details of particular
commits.

> Keep in mind that this is CVS and not a release system, and as
> developers, we reserve the right to break things.

Agreed. But bear in mind that as a user we reserve the right to inform
politely the developers that they broke things and if possible to fix
them at their convenient time. :-)

--
With kind regards,
Didier.

------------
Yum/apt repository for DR17/EFL: http://sps.nus.edu.sg/~didierbe

Didier F.B Casse
PhD candidate, Singapore Synchrotron Light Source (SSLS)
National University of Singapore.


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid3432&bid#0486&dat1642
_______________________________________________
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel

Reply via email to