[petsc-dev] Code for MAGMA solver

Harshad Sahasrabudhe hsahasra at purdue.edu
Tue Oct 8 21:55:40 CDT 2013


Hi Jed,

Santiago from my group thinks the following could be the cause of this bug:

If it is somehow useful : The problem seems to be that you are requesting a merge with the branch next and not with the branch master (which is the one you began from in the first place), and so all the commits that are on the master and are not yet in the branch "next" are being shown on this pull request.

Harshad

----- Original Message -----
From: "Jed Brown" <jedbrown at mcs.anl.gov>
To: "Harshad Sahasrabudhe" <hsahasra at purdue.edu>
Cc: "petsc-dev" <petsc-dev at mcs.anl.gov>
Sent: Tuesday, October 8, 2013 8:23:17 PM
Subject: Re: [petsc-dev] Code for MAGMA solver

Harshad Sahasrabudhe <hsahasra at purdue.edu> writes:

> Thanks Jed, that was very informative. I sent a pull request the correct way.

Thanks.  Github is displaying hundreds of commits here

https://github.com/petsc/petsc/pull/1

but only two are actually new, as shown here:

https://github.com/hsahasra/petsc/compare/petsc:next...hsahasra:magma-dense-mat

I haven't seen this before, but I filed a bug report with github.



More information about the petsc-dev mailing list