Hi Junio, I will change GitGitGadget to no longer Cc: you automatically. Please register my suspicion that this will make GitGitGadget a lot less useful: the stated mission of GitGitGadget is to make contributing patches to the Git project _easier_ so that the contributor can focus on the changes they want to make, rather than on the rather involved process. I know, you do not find any fault with the current process; it works for you. It just does not work all that well for many other people, myself included. The sheer amount of mostly unwritten, and not exactly static rules contributors are expected to follow are starting to remind me of Kafka's "The Trial". On Tue, 7 Jan 2020, Junio C Hamano wrote: > Besides, when they send out patches they would also add area experts and > those who participated in the review of the earlier round to Cc: so GGG > needs to have a mechanism to allow the end user to do so. So GitGitGadget should now also learn to determine who the current area experts are??? I must have misread your request. > And by treating the maintainer merely just one of the reviewer, that > mechanism can naturally be reused. Well, I certainly do not treat you as just one of the reviewers, as your complaints definitely keep me on my tip toes with regards to GitGitGadget. I do have to remind myself frequently that only two people ever complained about GitGitGadget, literally everybody else who is using GitGitGadget is quite happy. So maybe I should listen more to those positive voices. Actually, now that I wrote it, I think that is the only sane course of action here: listen more to positive voices. Ciao, Dscho
