tree a749d1ed750243874d690ed25266a4c9aeb89979
parent 18857e12579d841693c2dc39e9ee330ab36bca65
author Saša Živkov <sasa.zivkov@sap.com> 1557908014 +0200
committer Saša Živkov <sasa.zivkov@sap.com> 1558003952 +0200

When rescheduling due to in-flight push log also the in-flight task ID

When a push operation was rescheduled due to an in-flight push we logged
a line like:

   [79bda07a] Rescheduling replication to https://host/foo.git to avoid collision with an in-flight push.

This log was already useful but it didn't tell us which push task was
actually in-flight.

Add the ID of the in-flight push task to the log:

   [79bda07a] Rescheduling replication to https://host/foo.git to avoid collision with the in-flight push [80ceb18b].

This information is especially useful when a task gets repeatedly
rescheduled and we need to identify the root cause of that.

Change-Id: I7866f964cab1e4f479b0d7d62ae4aac3019fab4b