On 03/17/2014 09:33 AM, Jean-Marc Lasgouttes wrote:
The branch, master, has been updated. discards fa196dc15197a630a9c691bb7045bbe6eb293fad (commit) discards 5c9a1a1e92f78ab483930308934ef0ce764499ec (commit)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 (fa196dc15197a630a9c691bb7045bbe6eb293fad) \ N -- N -- N (264ea28cbd2a4c24dc6b81fa77422898167fa9f4) 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.
Did you really mean to do this? Note that this went to features/master. Richard
