Closed Dr-Emann closed 2 years ago
Yes, I know it is not very nice to this, but I intentionally rebased the master
branch on top of fixes-1.1.0
here.
I specifically don't want b71e8af and 664099f in the upcoming patch level release (this is part of a cleanup series that IMO still needs more time and I don't want to risk breaking something here). Also I'm not sure yet, if 72f9a50 should be part of a patch level release or not. On the other hand, the idea was to not fork off the fixes-1.1.0
branch just yet and having to cherry-pick back into master
all the time.
Okay, was just making sure it was intentional, thanks for the explanation.
Just want to check if this is intentional. I've seen master be force updated a few times recently. It looks like new commits are coming in, and the top two commits are being rebased on top of new changes, as far as I've checked, the diff content of the changed commits are identical: the hashes are changing only because of different parents.
Here's the history I've caught at least: Note that master used to point at f6d0563, and before that was at 5781bc7