Gitweb links:
...log
http://git.netsurf-browser.org/libcss.git/shortlog/57fa3608e13accc24a45e5d7801a381212c2ff22
...commit
http://git.netsurf-browser.org/libcss.git/commit/57fa3608e13accc24a45e5d7801a381212c2ff22
...tree
http://git.netsurf-browser.org/libcss.git/tree/57fa3608e13accc24a45e5d7801a381212c2ff22
The branch, master has been updated
discards 7a9dc81e71de235646af716f4482dc713520109f (commit)
discards 9e46e0f245f242c6f1b707016670caca2b57d428 (commit)
discards d4fef3c6ff5339888c7519fe7a2071c8e28da8f5 (commit)
via 57fa3608e13accc24a45e5d7801a381212c2ff22 (commit)
via f752713d07424217170c6fbf85789bd58d92f924 (commit)
via a0a52eb724f62d0df68c104108526e84148710bb (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 (7a9dc81e71de235646af716f4482dc713520109f)
\
N -- N -- N (57fa3608e13accc24a45e5d7801a381212c2ff22)
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.
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
-----------------------------------------------------------------------
Summary of changes:
--
Cascading Style Sheets library
_______________________________________________
netsurf-commits mailing list -- [email protected]
To unsubscribe send an email to [email protected]
