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 "pdl".
The branch, proj4fix has been updated
discards 9db924509c0dae17954f0f75745a4008468a40e1 (commit)
discards d4942be9d4c67ed0eb621492dbbd23da33e7f848 (commit)
discards a0b974a21c4deee14ee1c94b4d06e2e48c65ba35 (commit)
via 1932de1f8f5a52e153440f8bfe9438bc38049c51 (commit)
via 2d3fdf2b287fd96b7bd0dc6357f7a1c1d2c23d09 (commit)
via 0745da96ca2e13b9797cbd3c7849376e8517cedf (commit)
via 8467166ef77930085e896da24ff4bc042f19487e (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 (9db924509c0dae17954f0f75745a4008468a40e1)
\
N -- N -- N (1932de1f8f5a52e153440f8bfe9438bc38049c51)
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:
.travis.yml | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
hooks/post-receive
--
pdl
|
