Johannes Schindelin <Johannes.Schindelin@xxxxxx> writes: > I am afraid that I do not know of any means to teach GitGitGadget to make > that call whether it has seen a consensus. > > And I fear that you are asking me to punt back that decision to > contributors, i.e. put a lot of the burden of knowing how Git > contributions are expected to progress _away_ from GitGitGadget. Yes, and that is why I am giving review comments to contributors to teach how the development community works. > Of course, I can teach GitGitGadget to not Cc: you. Like, always. Not sure > that you would like that any better because you would not even be Cc:ed > once consensus was reached. That would actually be better. Somebody in the discussion thread would probably say "This is good enough---send it to the maintainer" when the topic is ready.
