unintended commit to sysvinit

[Tomas Pospisek]

Hello sysvinit maintainers,

expecting Gitlab to behave like Github when editing a file through the Web 
UI - that is that Gitlab would fork the project and create a patch branch 
for me - I have unintentionally done a commit [1] (and improved/fixed it 
[2] later).

In case the commit is OK like it is then I guess it can be 
left there otherwise I'm not sure how to proceed - revert the 
commit? Delete it and force-push?

I am very sorry for the inconvenience :-(

Greetings and thanks for maintaining sysvinit!
*t

[1] https://salsa.debian.org/debian/sysvinit/-/commit/75af55f59b562fea69adf7af8298ba0f777c9bb1
[2] https://salsa.debian.org/debian/sysvinit/-/commit/3dab939d570817d4203ef84f9e159740ae51a63a