debian-edu/slbackup.git (#2) - master (branch) updated: upstream/0.0.12-1-g7ffa9c6

The branch, master has been updated
  discards  611670c1dcc32462b6840a81d5a0eb9463dc694b (commit)
  discards  4bce76d32ce72dbdd91612206a0c0cc1970e93d0 (commit)
  discards  3245c203a9a7b214ab85b1cfbc9c7266266439a0 (commit)
  discards  4d2193877e6eb3c30c378f745a4cc263b6e6315e (commit)
  discards  76baa50e58387f49eac2a5adf5c9d1e2c6033680 (commit)
  discards  ab84ae9568b34bf19742a4f776344d2bcff53db2 (commit)
  discards  83de6c0abe83fe875e920cb2d1c29c0e150d8a08 (commit)
  discards  08892ba40ef09d06d0d3c1836f63950f210ae770 (commit)
  discards  db8c16a8e33e70257753bcdeb0b5a1ab50b2f2fb (commit)
  discards  68faa9a3287e6ecd1f948fa6df0afad218a1057f (commit)
  discards  4da09ce6ce5c5fbe693f36f191177724fe9f9123 (commit)
  discards  01c5a05bd2b1e36eeaf6d09a9e9a1b47b6f2afcb (commit)
  discards  818e5ef55778ac4f902cc141086812b99af7ccc1 (commit)
  discards  dc9d9ebc8e4a487654791965562ab3b11299283e (commit)
  discards  261bf6ac7238dbb908ea312267afd5c3ec0f7b60 (commit)
  discards  da97610fc4bd9fb23771ffef593add4a282396e3 (commit)
  discards  65b6d40835db688ef38390a45cf8860a94275070 (commit)
  discards  87d1f9a1f09c51ed8f521ea8430cc4236dd5101b (commit)
  discards  fefa2d72a39b84b7dc3e9223902d97bc174afe20 (commit)
  discards  0f30b35a426ef6ec370c19a6524460210d8546fa (commit)
  discards  abe15bd137e793f4944057124908cfe150186e2a (commit)
       via  7ffa9c6ccbd1dfb7eb3ef9fa25a438dc181a116e (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: