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 "Pd-extended".

The branch, patch_series has been updated discards 388f7e9098e8101edfdf953df869982f5410a0b3 (commit) discards aad5dca1241c48a1cd9c8e96f6fa10ed1ac4169b (commit) discards b5c3f16d934db041de66f4e57cef086ff5300f76 (commit) via 754bfc5620846f8dede427135722162045690bea (commit) via 19362f80349541b57b7470efd93d7c5c4294cc24 (commit) via 1ec7473acb88b49e4b1e51d23e9e17521b6540db (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 (388f7e9098e8101edfdf953df869982f5410a0b3) \ N -- N -- N (754bfc5620846f8dede427135722162045690bea)

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: tcl/pd_guiprefs.tcl | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-)

hooks/post-receive