This is an automated email from the git hooks/post-receive script.

Ryan Arnold pushed a change to branch linaro-local/releases/test-forcepush-linaro-6.1-2016.08 in repository toolchain/gcc.

omits ddfc2d4 Merge branch 'linaro-local/releases/linaro-6.1-2016.08' of ht [...] omits 4aaf125 gcc/ * LINARO-VERSION: Bump version number, post release ca [...] omits 82c3a18 Make Linaro GCC Release Candidate 6.1-2016.08-rc2. omits 9051b7c gcc/ * LINARO-VERSION: Bump version number, post release ca [...] omits 8ed4d5c Make Linaro GCC Release Candidate 6.1-2016.08-rc1. omits 2e55ddc gcc/ * LINARO-VERSION: Bump version number, post snapshot. new f571214 Make Linaro GCC Release Candidate 6.1-2016.08-rc1. new adf5e34 gcc/ * LINARO-VERSION: Bump version number, post release ca [...] new e5f5437 Make Linaro GCC Release Candidate 6.1-2016.08-rc2. new ec0d3c4 gcc/ * LINARO-VERSION: Bump version number, post release ca [...]

This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this:

* -- * -- B -- O -- O -- O (ddfc2d4) \ N -- N -- N refs/heads/linaro-local/releases/test-forcepush-linaro-6 [...]

You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B.

Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever.

The 4 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference.

Summary of changes: