[petsc-dev] petsc patch number

Kong, Fande fande.kong at inl.gov
Thu Apr 13 14:23:51 CDT 2017


In the moose side, we want to make some tests against the current maint,
but still have some tests against the old one. The two versions of petsc
may have the same petsc version number, e.g. 3.7.5. I want a patch number
from which I could tell which one is newer. How it is different from the
old one.

Any alternative way to do that? When compiling  PETSc, do we have a macro
variable to define the commit number?


On Thu, Apr 13, 2017 at 12:06 PM, Satish Balay <balay at mcs.anl.gov> wrote:

> On Thu, 13 Apr 2017, Kong, Fande wrote:
> > Hi Developers,
> >
> > Do we increase the patch number when pushing a new patch into maint?
> nope
> > If not, how to know if the current maint is different from the one I
> > just got yesterday. I know a commit number is always available.
> git fetch && git log maint..origin/maint
> [and you can look at that and decide to do a 'git pull' on maint]
> Satish
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20170413/27b0297d/attachment.html>

More information about the petsc-dev mailing list