Re: Any reason why wip/iverilog is waiting in the wings to replace cad/iverilog?

[Greg Troxel <gdt%lexort.com@localhost>]

Mayuresh <mayuresh%acm.org@localhost> writes:

> TODO just says this:
>
>     - Find ChangeLog
>
> That doesn't tell much.
>
> pkgsrc version is a good 8 years old now and 5 releases behind. wip has
> the latest release and I find it working.

wip norms call for COMMIT_MSG to be present and suitable for

  cvs commit -F COMMIT_MSG

so the TODO should arguably say "prepare COMMIT_MSG" instead of "find
changelog".