On 2017-05-30 16:07, Bartłomiej Piotrowski wrote:

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 "Official repo DB scripts".

The branch, master has been updated discards 14c1a41f27eb40dd4d85007632b01da84f7f5998 (commit) via f4085eaa30142ed778291c4e7dd6694c087bfaef (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 (14c1a41f27eb40dd4d85007632b01da84f7f5998) \ N -- N -- N (f4085eaa30142ed778291c4e7dd6694c087bfaef)

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 f4085eaa30142ed778291c4e7dd6694c087bfaef Author: Johannes Löthberg Date: Tue May 30 15:50:43 2017 +0200

config: add GPL3/LGPL3 to ALLOWED_LICENSES

Signed-off-by: Johannes Löthberg

-----------------------------------------------------------------------

Summary of changes:

hooks/post-receive

Sorry for spam, apparently using Thunderbird to get a patch wasn't the best idea (so I wanted to fix it). Bartłomiej