Skip to content
Snippets Groups Projects

Speed up CDEF

Closed Steinar Midtskogen requested to merge midtskogen/dav1d:master into master
2 unresolved threads

Unified x and y offsets of table lookup during filtering.

Merge request reports

Pipeline #317 passed

Pipeline passed for 3aaf6419 on midtskogen:master

Approved by

Closed by Ronald S. BultjeRonald S. Bultje 6 years ago (Sep 24, 2018 12:42pm UTC)

Activity

Filter activity
  • Approvals
  • Assignees & reviewers
  • Comments (from bots)
  • Comments (from users)
  • Commits & branches
  • Edits
  • Labels
  • Lock status
  • Mentions
  • Merge request status
  • Tracking
25 25 * SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
26 26 */
27 27
28 #include <assert.h>
  • 78 91 const int sec_strength, const int dir,
    79 92 const int damping, const enum CdefEdgeFlags edges)
    80 93 {
    81 const ptrdiff_t tmp_stride = w + 4;
    94 const ptrdiff_t tmp_stride = w == 4 ? 8 : 16;
  • added 1 commit

    Compare with previous version

  • added 1 commit

    Compare with previous version

  • +1 LGTM

  • Also, be careful, your name is incorrectly setup in this gitlab instance.

  • Oops, my name now has proper case.

  • Patch is OK. Could you rebase so we can merge?

  • added 19 commits

    Compare with previous version

  • Rebased. (The git history will be cleaner if we can squash the commits. I wasn't able to do that.)

  • I squashed it for you here: !27 (merged), is that OK with you?

  • Sure, go ahead merge.

    For future merge requests, is there a way to squash without making a new branch and merge request?

    The error I got after squashing locally was "Updates were rejected because the tip of your current branch is behind its remote counterpart", and force push didn't work either because I'm "not allowed to force push code to a protected branch on this project".

  • I typically use this:

    git fetch origin
    git rebase -i origin/master

    And then in the editor that pops up (showing your commits), for each (except the first) of the commits that you want to squash together, change "pick" on that line to "squash", save the commit-file and then force-repush to the same branch where you originally started the pull request from (so not origin/master, but midtskogen/master).

  • @midtskogen the master branch of all repositories/forks seems protected by default. git push -f if you use different branch name than master for merge requests

  • Yes, but I don't have permission to force push. I got things squashed fine locally and all looked good, but I was not able to push.

  • @jbk thinks it's because you were pushing to your personal master branch. It's personal, but by default it is still protected. You can unprotect it in the branch settings in your personal fork, but you could also simply use non-master for merge requests.

  • Please register or sign in to reply
    Loading