Hey, in theory you could rewrite history and force push an update, but that will break all commits on top of that.
I would create a revert patch, that restores the branch to its previuos state. History looks a bit more complicated after that, but that should not break others work. In general I would prefer if a committer commits bis work himself. He knows besteht how to handle it. Squash-and-merge is IMHO for corner cases and not for general usw. Matthias Am 28. Juni 2018 05:20:14 MESZ schrieb Junichi Yamamoto <junichi0...@gmail.com>: >Hi, > >My backport of fixes made after Apr 22, 2017 was merged into >2ndDonation branch[1]. However, it was squashed. I think that we >should not squash it. > >Can someone undo this? > >[1] https://github.com/apache/incubator-netbeans/pull/607 > >Thanks, >Junichi > >--------------------------------------------------------------------- >To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org >For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org > >For further information about the NetBeans mailing lists, visit: >https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists -- Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.
