Sean Whitton writes ("Bug#923732: dgit-infrastructure:
--deliberately-include-questionable-history required for every single push"):
> Package: dgit-infrastructure
> Version: 8.4
...
> swayidle was not actually ever rejected from NEW but was instead dcut
> from DEFERRED and uploaded again a few times.
AFAIAA there is no way for dgit-infrastructure or dgit to know whether
something was dcut or rejected.
> Shouldn't --deliberately-include-questionable-history be required only
> once? Shouldn't dgit-infrastructure learn that the commits it thinks
> are tainted aren't actually tainted?
Each time the thing is cut and repushed, presumably there are new
commits that might be tainted.
Ie,
push ...A
cut now ...A is tainted
push ...A+B needs reassurance that A is OK
cut now ...B is tainted
push ...A+B needs reassurance that A+B is OK
etc.
Don't you think ?
Ian.
