This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "notion window manager core".
The branch, master has been updated
discards a3995baf98c50c8150fd4fe36dbdf7d1325f9521 (commit)
via 4e628dee8a002ff74d2d734db2717d91f8360a3f (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 (a3995baf98c50c8150fd4fe36dbdf7d1325f9521)
\
N -- N -- N (4e628dee8a002ff74d2d734db2717d91f8360a3f)
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 -----------------------------------------------------------------
commit 4e628dee8a002ff74d2d734db2717d91f8360a3f
Author: Arnout Engelen <arn...@bz...>
Date: Tue May 27 22:50:23 2014 +0200
Actually make the windows key the default meta key
The documentation has already been updated in c688e57009b388c6b0586887ebee765a855c9958
-----------------------------------------------------------------------
Summary of changes:
ioncore/Makefile | 1 -
ioncore/ioncore_ext.lua | 4 ++--
2 files changed, 2 insertions(+), 3 deletions(-)
hooks/post-receive
--
notion window manager core
|
