From: Harald Nordgren Date: Mon, 02 Nov 2026 11:07:29 GMT Subject: Re: [PATCH v3] object-name: explain why ~N fails in a shallow clone Message-ID: In-Reply-To: <4836126b-e630-45cd-8757-861133ec233c@app.fastmail.com> > > Is it possible that maybe the review process needs to change if too > > many things are getting stuck? > > The regular reviewers have been talking about review work being scarce > compared to contributions (contributor work) for at least several years > now. How can this be changed if there simply aren’t enough people to > review everything? We can loosen the requirements on perfect code, as long as it does what it's supposed to and doesn't have security backdoors. Many things like tests, leaks and linting are already handled automatically by GitHub CI. It's a good time investment to automate more, because it frees up resources long-term. > > Rather than discarding acceptable work. > > My work which has been stuck is also acceptable to me. ;) But my > opinions are beside the point wrt. an independent review. Maybe we can trade reviews if you send me the link or links here? :) Harald