On Mon, 6 Jan 2014, Jed Brown wrote: > Satish Balay <[email protected]> writes: > > > But wrt URL - since we don't know where the docs will land - I can add > > in the following context to the message: > > > > Please describe the typo or error in the documentation: petsc-VER GIT-ID > > FILE-NAME > > > > i.e > > > > Please describe the typo or error in the documentation: petsc-dev > > 06283fd4323cef45a7147b2226c8e0c084e2a1d2 docs/manualpages/Vec/VecView.html > > > > http://ftp.mcs.anl.gov/pub/petsc/tmp/VecView.html is updated > > Looks good to me. > > > $ git diff |cat > > diff --git a/makefile b/makefile > > index 362c004..44d50cf 100644 > > --- a/makefile > > +++ b/makefile > > @@ -335,11 +335,13 @@ docsetdate: chk_petscdir > > fi; \ > > datestr=`git log -1 --pretty=format:%ci | cut -d ' ' -f 1`; \ > > export datestr; \ > > + gitver=`git log -1 --pretty=format:%H`; \ > > I would use "git describe" instead since it has some human-readable > context. > > v3.4.3-2283-g06283fd
Hm - we use 06283fd4323cef45a7147b2226c8e0c084e2 notation for PETSC_VERSION_GIT in petscconf.h [via configure] and in petscversion.h [during tarball generation] Should these also be changed to the new notation? Satish
