{"thread":{"id":"53433","subject":"Rebase merge backend","startedAt":"2020-05-08T14:35:16Z","lastAt":"2020-05-08T14:35:16Z","messageCount":1,"participants":["Nikolay Rykunov"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"397406","messageId":"CAES10x8wG_tBYZLrdyRAo=kU8B+gg65007Afs9jGdUUxL7kUBQ@mail.gmail.com","threadId":"53433","inReplyTo":null,"subject":"Rebase merge backend","fromName":"Nikolay Rykunov","fromEmail":"nikolay.rykunov@jetbrains.com","sentAt":"2020-05-08T14:35:00Z","receivedAt":"2020-05-08T14:35:16Z","isPatch":false,"sender":{"key":"nikolay.rykunov@jetbrains.com","avatar":null},"body":"Dear Git community,\nSince git rebase was moved to merge backend I can’t find the way how\nto get information that branch was fast-forwarded or it was up-to-date\n(it was provided by the apply backend). And a similar issue: I can’t\nget information about commits skipped during rebase because they\nbecame empty. Using apply backend I could check that because `No\nchanges — did you forget to use ‘git add’ ` line was printed. Can you\nplease help with these issues? Are there any ways to get such info?\n\nThank you!\nNikolay Rykunov\nSoftware Developer in VCS\nJetBrains\nhttp://www.jetbrains.com\nThe Drive to Develop\n"}]}