Hi, I made 4 commits with fixes for Altivec/VSX and pushed them to my fork at bitbucket (https://bitbucket.org/jaopaulolc/eigen/src/default/). How can I open a pull request? Regards,
You need to go to the pull-request menu of your fork and press the "create pull request" button there. Should that not work, you can also attach patches here.
(In reply to Christoph Hertzberg from comment #1) > You need to go to the pull-request menu of your fork and press the "create > pull request" button there. Should that not work, you can also attach > patches here. I tried that. But it throws an error: "We can't let you see this page" "To access this page, you may need to log in with another account. You can also return to the previous page or go back to your dashboard." So I thought it might be due to (lack of) permissions issues. Maybe it has something to due with my account been free?
(In reply to João Paulo Labegalini de Carvalho from comment #2) > (In reply to Christoph Hertzberg from comment #1) > > You need to go to the pull-request menu of your fork and press the "create > > pull request" button there. Should that not work, you can also attach > > patches here. > > I tried that. But it throws an error: > > "We can't let you see this page" > "To access this page, you may need to log in with another account. You can > also return to the previous page or go back to your dashboard." > > So I thought it might be due to (lack of) permissions issues. > > Maybe it has something to due with my account been free? Do'h! I was doing it on the official repo page, not on my fork. [Newbie detected!] Sorry for that!
*** Bug 1718 has been marked as a duplicate of this bug. ***
Please don't mark bugs as fixed before the fix is actually pushed into the repository. I now made this one the duplicate of the older bug (and re-opened that). *** This bug has been marked as a duplicate of bug 1718 ***
-- GitLab Migration Automatic Message -- This bug has been migrated to gitlab.com's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.com/libeigen/eigen/issues/1738.