Closed hmaarrfk closed 2 years ago
Hi! This is the friendly automated conda-forge-linting service.
I was trying to look for recipes to lint for you, but it appears we have a merge conflict. Please try to merge or rebase with the base branch to resolve this conflict.
Please ping the 'conda-forge/core' team (using the @ notation in a comment) if you believe this is a bug.
Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe
) and found it was in an excellent condition.
Can you post the diff of the two patches as a single patch here to make it easier to review? (No need to change the recipe, just post it in a comment here)
I believe @gmarkall did what you asked with: https://github.com/conda-forge/llvmdev-feedstock/pull/170/commits/9a818c13b0a7c980f8c1fcd62055870832c99f48
He kept the original patch intact.
A cleaned up git history can be found: https://github.com/conda-forge/llvmdev-feedstock/pull/171
No, I mean, one patch instead of two patches so that it's easier to review. (No need to push it, just paste it here)
I see. I can prepare that.
git checkout llvmorg-11.1.0
git apply /home/mark/git/feedstocks/llvmdev-feedstock/recipe/patches/llvm-consecutive-registers.patch
git apply /home/mark/git/feedstocks/llvmdev-feedstock/recipe/patches/llvm-consecutive-registers-abi.patch
Now that PR ( https://github.com/conda-forge/llvmdev-feedstock/pull/171 ) is in, would it make sense to close this or is there more needed from this PR that we would like to include?
Now that PR ( #171 ) is in, would it make sense to close this or is there more needed from this PR that we would like to include?
I don't see that there's anything else in here that wasn't in #171.
Given that #171 was merged, closing this as obsolete
Just testing the builds
Checklist
0
(if the version changed)conda-smithy
(Use the phrase code>@<space/conda-forge-admin, please rerender in a comment in this PR for automated rerendering)