New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Integrate changes from 2.6 RC2 #59
Conversation
If PREFIX isn't present for it too, the command will fail.
Hmmm... JEEB still hasn't mirrored the changes. Is there any indication he won't, or is he just slacking? Technically we don't need his branch and we could just mirror CVS in a branch of our own as you say, but if possible I'd like to avoid duplicating the whole history of Avisynth a 3rd time. |
I honestly don't know. The readme.md in the blitzkrieg branch has the exact command to perform it, and it can be done from the existing branch HEAD. The only thing the command is missing is the branch the changes should be merged into (so just append '-o target-branch' onto the end). I fetched JEEB's mirror into the 'classic_avisynth' branch on my repo, and since I wanted to keep things clean just in case he does update again, spawned off a 'classic_26rc2' branch where I used the command from readme.md to pull in the changes, and then did the migration work from there (and last night, pulled in the two RC3-related commits...neither of which are relevant to avsplus). |
Preliminarily, I've cherry-picked the only change that occurred between RC2/RC3 and 2.6 Final: the restoration of the GPL exception clause in avisynth.h. With this, we're caught up to 2.6.0 Final. If, however, it gets determined that we cannot do that to avisynth.h on our side because of the avsplus-specific changes that occurred based on the old exception-less alpha header, that commit can be omitted before merging. |
There's also been no movement on jeeb's repo over the past month and a half since I opened this PR, so I think we should mirror it ourselves. |
The JEEB has updated it now |
I'll merge from JEEB then. Thx for the heads up. |
I noticed earlier this morning that RC2 had been released a few days ago, so I did the same thing I did for RC1 and looked at what needed to be merged. The answer is a very underwhelming 'almost nothing', because most of the 14 commits that make up RC2 touch parts that have been removed from AviSynth+ entirely.
What made this more fun is that jeeb hasn't mirrored these commits yet (so the modifications to the RC2 commits and cherry-picking can't currently be forced over the old theirs history). With this in mind, #22 and this quirk could be solved by having a classic_avisynth branch where we can pull in CVS changes ourselves if we have to. I have such a branch pushed onto my repo.