Hi, > It is a solution but I prefer a word like svnrev.
:=) > > In this context, I recommend having a ChangeLog file at amforth root (as > recommended by GNU coding stadard) whose revision number is captured by > the a.m. word. I try to give every commit a meaningful change message, but I wont do that twice for every commit. Thus "svn log" *should have* given all you need, but on my system it prints only up to rev 1268, dropping anything that happens in trunk since then (4.9 was release around that rev). Strange. Anyway: sourceforge has quite a few tools installed that may give you the information you want: http://amforth.svn.sourceforge.net/viewvc/amforth?revision=1304&view=revision has a navigation feature, the RSS feed tells you all about what happens. Noteworthy changes are documented in the News section and at http://amforth.sf.net/. wrt the GNU coding style I like http://www.kernel.org/doc/Documentation/CodingStyle (2nd paragraph) with modifications ;=) Matthias ------------------------------------------------------------------------------ Monitor your physical, virtual and cloud infrastructure from a single web console. Get in-depth insight into apps, servers, databases, vmware, SAP, cloud infrastructure, etc. Download 30-day Free Trial. Pricing starts from $795 for 25 servers or applications! http://p.sf.net/sfu/zoho_dev2dev_nov _______________________________________________ Amforth-devel mailing list for http://amforth.sf.net/ Amforth-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amforth-devel
