On Thu, Oct 15, 2020 at 11:35:28AM -0700, Junio C Hamano wrote: > For this particular case, what we need is a functioning > patch tracker *and* people who pay attention to patches in the "came > very close to conclusion but no final patch in the tree" state. We > need people who can volunteer their eyeballs and attention to nudge, > prod and help patches to perfection, and that won't be me. Usually I'd expect this to be the responsibility of the patch submitter to make sure their stuff gets merged (and if not, to figure out why). Personally I make a branch for almost every patch/series I submit, no matter how trivial[1]. And then part of my daily ritual is seeing which ones have been merged, and dropping them. You can use git-cherry for that, though it's not 100% perfect (sometimes patches are munged as they are applied). I use a combination of that and aggressively rebasing patches forward (and eventually they rebase down into nothing when they've been fully merged). GitHub PRs can also serve as an open bookmark if people use them, but they're similarly not good at auto-closing because of our patch workflow (I don't know if GGG has any intelligence there, but it would presumably be subject to the same git-cherry issues). -Peff
