On Fri, May 28, 2021 at 9:33 AM Matthew Knepley <[email protected]> wrote:
> On Fri, May 28, 2021 at 9:16 AM Mark Adams <[email protected]> wrote: > >> How do you check out the version of PETSc used from the output: >> >> Using Petsc Development GIT revision: v3.15.0-531-g1397235 GIT Date: >> 2021-05-18 13:47:28 -0400 >> >> I am looking for a SHA1 >> > > You should be able to lookup the commit from the short hash > > git show 1397235 > > but that hash is not in my repo. > Thanks everyone. How would I get a version (a branch say) to be and stay visible? I am not seeing any of my versions used for this data but they were all in the repo at one point, in a branch. Does the branch need to be merged with main? I am going to rerun all the data anyway, so I now want to understand how to set up a branch to use everywhere and, of course, stay visible (for a few months at least). > > Matt > > >> Thanks, >> Mark >> > > > -- > What most experimenters take for granted before they begin their > experiments is infinitely more interesting than any results to which their > experiments lead. > -- Norbert Wiener > > https://www.cse.buffalo.edu/~knepley/ > <http://www.cse.buffalo.edu/~knepley/> >
