Files
weave-scope/client/app/scripts/components
Damien Lespiau 53f1890ad7 tracking: Fix in-flight collision of two related PRs
Unfortunately, I forgot to rebase before renaming trackMixpanelEvent() and a PR
adding a new trace point was already in-flight.

More precisely:
  - https://github.com/weaveworks/scope/pull/2861 renames trackMixpanelEvent()
    to trackAnalysticsEent()
  - https://github.com/weaveworks/scope/pull/2857 add a new
    trackMixpanelEvent() call.

Each PR is fine, but with the merge of both without rebasing any, we end up
with master having a dandling call to trackMixpanelEvent().
2017-09-26 12:59:29 +01:00
..
2017-05-04 13:12:00 +02:00
2017-02-20 11:10:44 +01:00
2017-05-04 13:12:00 +02:00
2016-05-11 18:08:59 +02:00
2017-02-20 11:10:44 +01:00
2016-08-03 08:50:37 +02:00
2017-07-06 16:06:55 +02:00
2017-05-15 11:49:12 +02:00