[petsc-users] [petsc-dev] [SLEPc] For users of PETSc master branch, API change

[Satish Balay]

you can try using a slightly older 'master' snapshot' [until you get
the slpec fix]

For eg:
git checkout d916695f21d798ebdf80dc439ef54c5223c9183c

And once the slepc fix is available - you can do:
git checkout master
git pull

Satish

On Mon, 9 Nov 2015, Leoni, Massimiliano wrote:

> Ok, sorry!
> It looks like I chose the worst possible day to update :D
> 
> Best,
> 
> Massimiliano
> 
> > -----Original Message-----
> > From: Jose E. Roman [mailto:jroman at dsic.upv.es]
> > Sent: 09 November 2015 14:26
> > To: Leoni, Massimiliano
> > Cc: Barry Smith; PETSc; petsc-dev
> > Subject: Re: [petsc-dev] [SLEPc] For users of PETSc master branch, API
> > change
> > 
> > Working on it. Be patient. Should be available on master tomorrow.
> > Jose
> > 
> > 
> > 
> > > El 9/11/2015, a las 15:23, Leoni, Massimiliano <Massimiliano.Leoni at Rolls-
> > Royce.com> escribió:
> > >
> > > Is there a branch in the SLEPc repo that supports this?
> > >
> > > Massimiliano
> > >
> > >> -----Original Message-----
> > >> From: petsc-dev-bounces at mcs.anl.gov [mailto:petsc-dev-
> > >> bounces at mcs.anl.gov] On Behalf Of Barry Smith
> > >> Sent: 09 November 2015 00:21
> > >> To: PETSc; petsc-dev
> > >> Subject: [petsc-dev] For users of PETSc master branch, API change
> > >>
> > >>
> > >>   For users of the PETSc master branch.
> > >>
> > >>   I have pushed into master some API changes for the
> > >> PetscOptionsGetXXX() and related routines. The first argument is now
> > >> a PetscOptions object, which is optional, if you pass a NULL in for
> > >> the first argument (or a PETSC_NULL_OBJECT in Fortran) you will
> > >> retain the same functionality as you had previously.
> > >>
> > >>   Barry
> > >
> > > The data contained in, or attached to, this e-mail, may contain confidential
> > information. If you have received it in error you should notify the sender
> > immediately by reply e-mail, delete the message from your system and
> > contact +44 (0) 3301235850 (Security Operations Centre) if you need
> > assistance. Please do not copy it for any purpose, or disclose its contents to
> > any other person.
> > >
> > > An e-mail response to this address may be subject to interception or
> > monitoring for operational reasons or for lawful business practices.
> > >
> > > (c) 2015 Rolls-Royce plc
> > >
> > > Registered office: 62 Buckingham Gate, London SW1E 6AT Company
> > number: 1003142. Registered in England.
> > >
> 
> The data contained in, or attached to, this e-mail, may contain confidential information. If you have received it in error you should notify the sender immediately by reply e-mail, delete the message from your system and contact +44 (0) 3301235850 (Security Operations Centre) if you need assistance. Please do not copy it for any purpose, or disclose its contents to any other person.
> 
> An e-mail response to this address may be subject to interception or monitoring for operational reasons or for lawful business practices.
> 
> (c) 2015 Rolls-Royce plc
> 
> Registered office: 62 Buckingham Gate, London SW1E 6AT Company number: 1003142. Registered in England.
>