Thanks, Maksim. Anyway, I suggest to notify community just about such cases for better transparency.
чт, 16 мар. 2023 г. в 12:52, Maksim Timonin <timoninma...@apache.org>: > Hi, Peter! > > Yes, I've pushed to the master branch. Actually it was a fix of the commit > message. There was about 1 min difference between original commit and the > fix. > > I checked master before the fix, and actually it happened at night. Usually > no commits are performed this time. > > Sorry, for doing that :( it was an exceptional case. > > чт, 16 мар. 2023 г., 10:18 Peter Ivanov <vvei...@apache.org>: > > > Hi, Igniters! > > > > Recently I've noticed that somehow the history of the *master* branch of > > apache/ignite project has been changed. > > The changed commit is the following: > > *Thu Mar 9 22:52:10 2023 +0300 : Thu Mar 9 22:59:03 2023 +0300 a8e1689951 > > (2023-03-09 22:59:03 +0300) Maksim Timonin <timonin.ma...@gmail.com > > <timonin.ma...@gmail.com>> IGNITE-17177 Added incremental snapshots > > (#10539)* > > Previous hash was 04304d4e9e > > > > As it seems, someone (supposedly Maksim himself) updated the master > branch > > with forced history rewriting. > > > > So the questions are: > > 1. Why? Was there a serious reason to do so, breaking all processes > > connected to master branch update? > > 2. How? Do we not have limitations for master branch rewriting? > > >
