> > This update added new revisions after undoing existing revisions. That is > to say, the old revision is not a strict subset of the new revision. This > situation occurs when you --force push a change and generate a repository > containing something like this: > > * -- * -- B -- O -- O -- O (36f6605f81b7c067c393ffb529916cf024b16c73) > \ > N -- N -- N (2110fd04fb78978d8e3dfd7570bafe348766ddbe) > > When this happens we assume that you've already had alert emails for all > of the O revisions, and so we here report only the revisions in the N > branch from the common base, B.
Cool, I think... how did that happen & what does it mean? Keith _______________________________________________ mesa-commit mailing list mesa-commit@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-commit
