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
MR1: Remove special case for Cygwin for BLAS detection when installing fflas_ffpack #26353
Comments
This comment has been minimized.
This comment has been minimized.
comment:3
First attempt at merge request synced from gitlab. A few bugs that happened (which for some reason didn't happen in testing):
The rest seemed to work OK. It will be good to have a mechanism to set other fields such as component and type, but for now I don't have a mechanism for that and instead assume it should be left up to project maintainers to set those fields. |
comment:4
New commits added to merge request. I updated the commit SHA-1. This was a forced push. New commits:
|
comment:5
You probably want a mechanism to set the real name in the authors field too as otherwise this ticket will get reverted back from a positive review. Should I do the review from the gitlab side or from the Sage side? |
comment:6
Replying to @tscrim:
That's a good point. The names would have to match up though (or, I suppose, the release manager can always update the "trusted names" list.
Whichever you prefer. |
Author: Erik Bray |
comment:8
LGTM. |
Reviewer: Travis Scrimshaw |
comment:9
Just deployed an update to the bot which should address all the issues raised in this initial test ticket :) |
Changed branch from u/galois/mrs/1/embray/cygwin/fflas_ffpack/simplify-blas to |
<img src="https://secure.gravatar.com/avatar/c7d341e2b002754f2b21fbab3a3fd072?s=80&d=identicon" right, margin=5> Erik Bray (@embray) opened a merge request at https://gitlab.com/sagemath/sage/merge_requests/1:
Component: porting: Cygwin
Author: Erik Bray
Branch/Commit:
09e289a
Reviewer: Travis Scrimshaw
Issue created by migration from https://trac.sagemath.org/ticket/26353
The text was updated successfully, but these errors were encountered: