eine

If it is not much effort, please do. I started having a look at it, but I'm finding it difficult to understand where are commands defined. For example https://github.com/ghdl/ghdl/blob/master/src/ghdldrv/ghdlcomp.adb#L127 and...

Coming from [#1362](https://github.com/ghdl/ghdl/issues/1362#issuecomment-641423542), perhaps we should consider adding `--sim` or `--simulate` as the "long form" of `-c`. That would make it more explicit that both are the "higher-level" (single command)...

Is that a technical limitation or a not implemented feature? My idea would be to support `-c [options] file... - primary_unit [secondary_unit] [simulation_options...]` meaning that `-c` is "equivalent to appending...

Hi José! I think that feature is not supported for simulation yet. See #24.

Please, let us know the origin of the GHDL executable that you are using. I assume that you built it from sources; which commit SHA did you use?

> Tags are fixed references in Git, whereas branches are sliding references. As the stable pointer will be moved over time, I suggest to use a branch. Sliding tags are...

> I would not suggest to change the default branch. git clone should always fetch the latest stable version, but not a development version. I users want to build from...

This is a 2-3 branch model that will most of the time be a single branch in practice, as it is now: [ghdl-branching-model.pdf](https://github.com/ghdl/ghdl/files/1669939/ghdl-branching-model.pdf) - Even though R0 and R1 are...

> I'm against fast-forward merges for feature branches. Indeed, it is not required at all. I replaced it with a fast-forward (pull). I believe that the rest of your comments...

@go2sh I agree about keeping a single main branch (for release and integration). But, at the same time, we need some model (as simple as it can be) to handle...