The branch, bug/15495 has been updated
Old revision: 0b4adcfba14cf43d1a637879d5aa94b9245d90d2, new revision: ad99845c074fca9e5d21a2cd1dbc21ebafe4be4a.
discards 0b4adcfba14cf43d1a637879d5aa94b9245d90d2 (commit)
via ad99845c074fca9e5d21a2cd1dbc21ebafe4be4a (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 (0b4adcfba14cf43d1a637879d5aa94b9245d90d2)
\
N -- N -- N (ad99845c074fca9e5d21a2cd1dbc21ebafe4be4a)
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.
- Log -----------------------------------------------------------------
commit ad99845c074fca9e5d21a2cd1dbc21ebafe4be4a
Author: Jack Twilley <
j...@osuosl.org>
Date: Thu Dec 19 14:44:08 2013 -0800
Modified documentation to reflect change in console support.
We will be supporting graphical and serial consoles, so I have changed
the documentation to reflect that change. Optimistic, but I have to
start somewhere.
refs #15495
Summary of changes: