"Philip Oakley" <philipoak...@iee.org> writes: > It may even be worth 'splitting' the pu branch sequence into the > existing pu (with merges from series that are selected as reasonable), > and then a pr branch (public review?) on top of that holding the rest > of the series that have been submitted, so that the CI can do a full > test on the tips of them to support those devs with limited test > capability.
I won't stop you from publishing such a pr branch yourself. For patches whose merit is not clear because the problem they try to solve is under-explained, whose solution is ill-designed, etc., IOW, with issues that makes me judge that they are not interesting enough for 'pu', it is not worth my time to deal with whitespace brekages in them to make them not even apply, to figure out what base the patches are meant to apply to, or to resolve conflicts caused by them with topics already in flight, etc.
