BTW, we should put the ":" between the time format if we use the command "date --iso-8601=seconds". For example, > 2007-10-08T20:03:56-0400 -> 2007-10-08T20:03:56-04:00
Without the ":", opkgc will complain about it. Regards, - DongInn Bernard Li wrote: > Hi Erich: > > On 10/8/07, Erich Focht <[EMAIL PROTECTED]> wrote: > >> Thanks, didn't look to the ganglia mailing list since a while... Will update >> the package asap. > > I just updated it. > > BTW, looking at the new config.xml format, the field "date" in > <changelogEntry> seems to all have the same time -- I guess it's > probably because folks do not know how the timestamp is generated. > The closest match I could find was: > > date --iso-8601=seconds > > But anyways, is the time really useful here? Or is the date sufficient? > > Cheers, > > Bernard > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > Oscar-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/oscar-devel ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Oscar-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/oscar-devel
