Next | Query returned 45 messages, browsing 31 to 40 | Previous

History of commit frequency

CVS Commit History:


   2006-08-22 19:00:24 by Joerg Sonnenberger | Files touched by this commit (17)
Log message:
Naming a type "signal" is a bad idea since a compatibility function of
that name exists and GCC 3.4 complains about it. Rename it to signal_s.
   2006-02-06 00:11:50 by Joerg Sonnenberger | Files touched by this commit (4082)
Log message:
Recursive revision bump / recommended bump for gettext ABI change.
   2005-07-16 03:19:27 by Johnny C. Lam | Files touched by this commit (273)
Log message:
Get rid of USE_PERL5.  The new way to express needing the Perl executable
around at either build-time or at run-time is:

	USE_TOOLS+=	perl		# build-time
	USE_TOOLS+=	perl:run	# run-time

Also remove some places where perl5/buildlink3.mk was being included
by a package Makefile, but all that the package wanted was the Perl
executable.
   2005-05-22 22:08:52 by Johnny C. Lam | Files touched by this commit (1035)
Log message:
Remove USE_GNU_TOOLS and replace with the correct USE_TOOLS definitions:

	USE_GNU_TOOLS	-> USE_TOOLS
	awk		-> gawk
	m4		-> gm4
	make		-> gmake
	sed		-> gsed
	yacc		-> bison
   2005-04-11 23:48:17 by Todd Vierling | Files touched by this commit (3539)
Log message:
Remove USE_BUILDLINK3 and NO_BUILDLINK; these are no longer used.
   2005-03-01 01:13:45 by Dan McMahill | Files touched by this commit (4) | Package updated
Log message:
fix fallout from bison-2.0 update
   2005-02-23 15:59:26 by Alistair G. Crooks | Files touched by this commit (50)
Log message:
Add RMD160 digests in addition to SHA1 ones.
   2004-11-27 16:04:02 by Dan McMahill | Files touched by this commit (2) | Package updated
Log message:
update to covered-0.3

Changes since the last stable release:

  - User-specified FSM code coverage.  By using command-line options or inline \ 
code specified
    by the user, FSM code coverage can be extracted from the design.  This does \ 
not include
    the ability to automatically extract FSMs from the design (an ability that \ 
will be added
    in future stable releases).
  - Enhanced performance of the score command.  A 3x - 5x speedup in the running \ 
time of the
    score command on the design should be expected with this release over past \ 
stable releases.
  - Enhanced readability of coverage reports.  The coverage report look has been \ 
overhauled to
    produce a much more readable/understandable coverage report.
  - Several bug-fixes have been made, including coverage number calculation bugs.
  - Development and user documentation updates.
  - Enhanced regression suite.
   2004-03-12 23:37:12 by Dan McMahill | Files touched by this commit (2)
Log message:
bl3ify
   2004-02-01 00:32:11 by Soren Jacobsen | Files touched by this commit (1)
Log message:
s/seperate/separate/

Next | Query returned 45 messages, browsing 31 to 40 | Previous