Pete Grayson

It might be worth reviewing the characteristics of the LXT and FST dump formats supported by GTKWave. Details are in the GTKWave manual: http://gtkwave.sourceforge.net/gtkwave.pdf. I don't know how amenable either...

I'm glad pyvcd is working for you! And thank you for identifying this issue. The `name` parameter to `register_var()` corresponds to the "reference" in the IEEE 1364-2005 specification (see BNF...

PyVCD has optimizations to both avoid writing superfluous value changes when the value doesn't change as well as only writing timestamps in conjunction with value changes (to avoid superfluous timestamps)....

I'm not categorically opposed to StGit having this kind of feature. But I do want to be careful about only adding features that are generally useful and have a good...

If that covers your use cases, it make sense to me to do it that way.

This is an interesting idea, @lthms. I think it is worth looking into. My next step will be look at the mechanism `git` uses to do this and evaluate whether...

Since you're referencing `stg mail`, can I assume you're using StGit 1.x? In StGit 2.0, `stg mail` was replaced with `stg email format` and `stg email send` which are thin...

If I'm understanding the request, this feature would associate patches based on whether and where merge conflicts emerge. I think that's an interesting idea; I hadn't considered it before. That...

From ieee 1364-2001: > The value change dumper generates character identifier codes to represent variables. The identifier code is a code composed of the printable characters which are in the...

Setting `commit.gpgsign = true` and `stg.gpgsign = false` should result in regular patch commits being signed. I typically run with this setup and it works for me. I'm sorry it...