Re: [petsc-dev] unwind next branch

2014-09-10 Thread Matthew Knepley
On Tue, Sep 9, 2014 at 6:33 PM, Satish Balay wrote: > On Tue, 9 Sep 2014, Jed Brown wrote: > > > Satish Balay writes: > > > > > Jed, > > > > > > After 3.5 release we have not unwound next branch. > > > > > > With 3.5.2 out - is it a good time to unwind? > > > > > > This might need some coordinat

Re: [petsc-dev] unwind next branch

2014-09-10 Thread Jose E. Roman
> origin/jose/mumps-bugfix --> remove (those fixes have already been included in other commits by Hong.) Jose

Re: [petsc-dev] PetscSplitReduction

2014-09-10 Thread Jose E. Roman
El 09/07/2014, a las 23:39, Jed Brown escribió: > Satish Balay writes: > >> merged to maint now. > > Satish, we can't have this non-namespaced stuff in 'maint' (it really > can break user code). The struct definition should really be private > (so if Jose needs to access fields, we need to wr

Re: [petsc-dev] unwind next branch

2014-09-10 Thread Stefano Zampini
Please keep all my branches not yet merged to master 2014-09-10 2:33 GMT+03:00 Satish Balay : > On Tue, 9 Sep 2014, Jed Brown wrote: > > > Satish Balay writes: > > > > > Jed, > > > > > > After 3.5 release we have not unwound next branch. > > > > > > With 3.5.2 out - is it a good time to unwind?

Re: [petsc-dev] unwind next branch

2014-09-10 Thread Abhyankar, Shrirang G.
You can delete origin/shri/external-package-KLU origin/shri/feature-dm-circuit Please keep all the other branches. Thanks, Shri -Original Message- From: satish balay Date: Tue, 9 Sep 2014 17:50:58 -0500 To: petsc-dev mailing list Subject: [petsc-dev] unwind next branch >Jed, > >Aft

Re: [petsc-dev] unwind next branch

2014-09-10 Thread Satish Balay
Shri, You have multiple branches merged to next - but not to master. And they appear to be more than a year old.. > origin/shri/ts-dae-semi-explicit > origin/shri/ts-is-for-differential-variables > origin/shri/ts-powergrid Satish On Wed, 10 Sep 2014, Abhyankar, Shrirang G. wrote: > You can

Re: [petsc-dev] unwind next branch

2014-09-10 Thread Satish Balay
I deleted the following branches at bitbucket: origin/barry/add-snespseudo origin/barry/august-tutorial origin/barry/twitter origin/knepley/dmswarm origin/knepley/sr-driver origin/jose/mumps-bugfix origin/shri/external-package-KLU origin/shri/feature-dm-circuit Also deleted t

[petsc-dev] updates to handling of external packages

2014-09-10 Thread Barry Smith
PETSc developers, As many of you know I have been cleaning up the PETSc handling of external packages including the support for —download-. I am close to being done, the major changes are 1) there is no distinction between “PETSc” and BuildSystem packages, they are now all in confi

Re: [petsc-dev] PetscSplitReduction

2014-09-10 Thread Barry Smith
Jose, Start by making PetscSplitReduction an opaque pointer to the actual struct. For example typedef struct _n_PetscSplitReduction *PetscSplitReduction; goes in the public include include/petscsys.h typedef struct { - MPI_Commcomm; - MPI_Request request; - PetscBool asyn

[petsc-dev] Parmetis test ex152.c fails on 64 bit integers

2014-09-10 Thread Barry Smith
Jed, This test is failing on me with —with-64-bit-indices. It seems to be reading binary from some data file so I suspect the data file is wrong for 64 bit integers but the example does no test on integer size. Is this test suppose to work for —with-64-bit-indices or should it have

Re: [petsc-dev] Parmetis test ex152.c fails on 64 bit integers

2014-09-10 Thread Jed Brown
Barry Smith writes: > Jed, > > This test is failing on me with —with-64-bit-indices. It seems to > be reading binary from some data file so I suspect the data file > is wrong for 64 bit integers but the example does no test on > integer size. Yes, it uses sizeof(idx_t) when re