osmo-ggsn.git branch laforge/gpdu-seq updated. 1.0.0-18-gfbb9c7f

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 "The OpenGGSN project". The branch, laforge/gpdu-seq has been updated discards 808b4ced0bb64181e18ff47dfc952f30829e5de1 (commit) discards e21c3e4f5ebfeb33ef24d3af069063983ed5dd08 (commit) discards 01b25c7389e8000a2ac7b3c019374687552b6b6c (commit) via fbb9c7f59a7f112608b59c7692c1fddd1a5e8c23 (commit) via 93fed3bc510563e7d88cadafa7eada2ae4182213 (commit) via 3c1cce245e6ed1746c0eacc6208b884871186d3d (commit) via 00d346092be0b9d948f687efb4b20a0727019b71 (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 (808b4ced0bb64181e18ff47dfc952f30829e5de1) \ N -- N -- N (fbb9c7f59a7f112608b59c7692c1fddd1a5e8c23) 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: ggsn/ggsn_vty.c | 2 ++ 1 file changed, 2 insertions(+) hooks/post-receive -- The OpenGGSN project