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 ddd3b6e74af0b471034c2883aa994eda16a2ae0d (commit) via ca0b83cb5b8523ab87a758a1d1af56f4f356c4b4 (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 (ddd3b6e74af0b471034c2883aa994eda16a2ae0d) \ N -- N -- N (ca0b83cb5b8523ab87a758a1d1af56f4f356c4b4)

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 ca0b83cb5b8523ab87a758a1d1af56f4f356c4b4 Author: Hans-Christoph Steiner hans@eds.org Date: Tue Nov 8 10:55:35 2011 -0500

REBASE into "implement PD_BIGORSMALL() with unions"

- renamed PD_FLOATSIZE to PD_FLOATPRECISION

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

Summary of changes: src/m_pd.h | 10 +++++----- 1 files changed, 5 insertions(+), 5 deletions(-)

hooks/post-receive