Skip to content

Only run legacy appveyor ci on github master branch#325

Closed
xnorpx wants to merge 4 commits intoxiph:mainfrom
xnorpx:fix/appveyor
Closed

Only run legacy appveyor ci on github master branch#325
xnorpx wants to merge 4 commits intoxiph:mainfrom
xnorpx:fix/appveyor

Conversation

@xnorpx
Copy link
Contributor

@xnorpx xnorpx commented Mar 19, 2024

WIP, don't apply this patch yet......

jmvalin and others added 4 commits August 11, 2023 04:06
This only affects custom modes (builds with --enable-custom-modes) with frame
sizes 2.5, 5, 10, and 20ms and sampling rates below 40 kHz. The problem does
not affect normal use of Opus (using OpusEncoder/OpusDecoder) even when built
with custom modes enabled, but only special applications that use
OpusCustomEncoder/OpusCustomDecoder.
Co-authored-by: James Zern <jzern@google.com>
Update silk/x86/NSQ_del_dec_sse4_1.c to match the remaining
silk/NSQ_del_dec.c changes made in
https://gitlab.xiph.org/xiph/opus/-/commit/c913dc38
@xnorpx xnorpx changed the base branch from master to main March 19, 2024 02:02
@jmvalin
Copy link
Member

jmvalin commented Mar 19, 2024

Actually, the only reason there's still a master branch is that I haven't found a way to delete it. I already deleted it on gitlab.xiph.org. Any idea how to also delete it on the github mirror?

@xnorpx
Copy link
Contributor Author

xnorpx commented Mar 19, 2024

@jmvalin ah that's even better.

Based on the documentation, you should be able to delete it once you changed the default branch.

But maybe you need to close all PR's that still pointing to master?

https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository

Maybe close all open PR's that points to master and ask the authors to reopen against main if they still are relevant and interested.

If the branch you want to delete is associated with an open pull request, you must merge or close the pull request before deleting the branch.

It also looks like there is 3 commits' on master that is not on main if they are still relevant in any way.

@xnorpx
Copy link
Contributor Author

xnorpx commented Mar 19, 2024

Closing as master branch will be removed (once it's known how to)

@xnorpx xnorpx closed this Mar 19, 2024
@jmvalin
Copy link
Member

jmvalin commented Mar 19, 2024

Well, I think I found how to delete it. Side effect is that I think it just closed all PRs for master

@xnorpx
Copy link
Contributor Author

xnorpx commented Mar 19, 2024

Well, I think I found how to delete it. Side effect is that I think it just closed all PRs for master

Good to clean house :)

Master branch is deleted and all pr's against master is closed. If this change is still relevant please reopen and repoint your PR to main branch.

@mark4o
Copy link
Contributor

mark4o commented Mar 19, 2024

These open PRs were automatically closed when the "master" branch was deleted: #109, #143, #153, #187, #210, #233, #250, #257, #262, #285, #304. Those that are still relevant should be rebased against the "main" branch instead of "master" and reopened.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants