Re: [Gnu-arch-users] GCC v. Arch address@hidden: Regressions on mainline]

[Tom Lord]

    > From: Andrew Suffield <address@hidden>

    > Huh, interesting timing. I've been thinking about this problem for a
    > week or two, and started to put together some of the intrastructure it
    > needs.

    > Certainly gcc is a good example of a project which this problem, but
    > I'm not convinced their approach is the best solution. A PQM-driven
    > mainline that only allows commits which do not cause regressions is
    > probably what they really want. But it's easy enough to handle what
    > they currently do.

I thought about a PQM-driven Aegis-like protected mainline but I don't
think it works out unless you do it in a _fairly_ hairy way.

GCC commits happen too fast (last I checked) to serialize them while
inserting tests between each one.

I.e., just naively dropping a "make test" call into your PQM just
before the "tla commit" --- probably the commit queue will grow
without bound (until the developers notice and say, hey, this isn't
working :-).

-t