[petsc-dev] All petsc-dev users will need to do a reclone of petsc-dev on Tuesday or later

2013-03-11 Thread Richard Tran Mills
1) Jed, what did you do to Barry? =) 2) I am am going to interpret the move from Mercurial to Git as a sign that the End Times are indeed here. OK, seriously, I am OK with using Git or Mercurial: I think they are actually fairly similar tools and each has pluses and minuses. But what I do want

[petsc-dev] All petsc-dev users will need to do a reclone of petsc-dev on Tuesday or later

2013-03-11 Thread Karl Rupp
Hi Richard, it will still be possible to pull from a Mercurial repository, which is in sync with the HEAD of the stable master-branch in git. We will also continue to accept pull requests via Mercurial, so no apocalypse :-) Best regards, Karli On 03/11/2013 10:08 PM, Richard Tran Mills wrote

[petsc-dev] All petsc-dev users will need to do a reclone of petsc-dev on Tuesday or later

2013-03-11 Thread Barry Smith
On Mar 11, 2013, at 10:08 PM, Richard Tran Mills wrote: > 1) Jed, what did you do to Barry? =) > 2) I am am going to interpret the move from Mercurial to Git as a sign that > the End Times are indeed here. > > OK, seriously, I am OK with using Git or Mercurial: I think they are actually > fai

[petsc-dev] possible bug in MatLoad_MPIBAIJ()

2013-03-11 Thread Lisandro Dalcin
Please review and apply the following patch for release-3.3 (if it is OK, should be pushed to dev, too). diff -r ec5e51fd886c src/mat/impls/baij/mpi/mpibaij.c --- a/src/mat/impls/baij/mpi/mpibaij.c Sat Mar 09 10:50:47 2013 -0600 +++ b/src/mat/impls/baij/mpi/mpibaij.c Mon Mar 11 21:19:18 2013 +030

[petsc-dev] [mpich-discuss] MPICH migration to git

2013-03-11 Thread Jed Brown
- next part -- An HTML attachment was scrubbed... URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20130311/03ac853e/attachment.html>

[petsc-dev] Usability

2013-03-11 Thread Matthew Knepley
n any results to which their experiments lead. -- Norbert Wiener -- next part -- An HTML attachment was scrubbed... URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20130311/33e9d822/attachment.html>

[petsc-dev] Usability

2013-03-11 Thread Jed Brown
merged into the current branch and 'git branch --no-merged' for the converse. Add '-v' for more details about the branch. Is this what you were looking for? -- next part -- An HTML attachment was scrubbed... URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20130311/0a61708b/attachment.html>

[petsc-dev] Cache blocking ex2.c

2013-03-11 Thread Nystrom, William D
This weekend, I spent some time making a modified version of src/ksp/ksp/examples/tutorials/ex2.c where I added the capability to divide the m x n mesh into blocks of size mblk x nblk respectively. I believe I have this debugged and working properly. In building the matrix, I travel through th

[petsc-dev] Usability

2013-03-11 Thread Jed Brown
ter want to find it, it will still be in the reflog $ git reflog --grep "something relevant" -- next part -- An HTML attachment was scrubbed... URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20130311/8e4cf954/attachment-0001.html>

[petsc-dev] Usability

2013-03-11 Thread Satish Balay
As I understand it [from discussing with Jed] - 'git HEAD' is equivalent to 'hg parent'. But I'm not sure what the equivalent of 'hg head' is. [which is where all dangling heads would be captured - and hg would warn/force a merge - before push] Satish On Mon, 11 Mar 2013, Matthew Knepley wrote:

[petsc-dev] Usability

2013-03-11 Thread Jed Brown
you what is screwed up. > Sure, and we can add to it as we learn more ways that people can get lost. Using __git_ps1 helps a lot. -- next part -- An HTML attachment was scrubbed... URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20130311/edb916f9/attachment.html>

[petsc-dev] [mpich-discuss] MPICH migration to git

2013-03-11 Thread Sean Farley
On Mon, Jan 21, 2013 at 11:42 AM, Jed Brown wrote: > > On Mon, Jan 21, 2013 at 11:18 AM, Sean Farley > wrote: >> >> On Mon, Jan 21, 2013 at 11:03 AM, Jed Brown wrote: >> > >> > On Mon, Jan 21, 2013 at 10:53 AM, Sean Farley >> > wrote: >> >> >> >> Well ? did you try this with the equivalent merc

[petsc-dev] All petsc-dev users will need to do a reclone of petsc-dev on Tuesday or later

2013-03-11 Thread Matthew Knepley
st experimenters take for granted before they begin their experiments is infinitely more interesting than any results to which their experiments lead. -- Norbert Wiener -- next part -- An HTML attachment was scrubbed... URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20130311/98941c84/attachment-0001.html>

[petsc-dev] All petsc-dev users will need to do a reclone of petsc-dev on Tuesday or later

2013-03-11 Thread Hong Zhang
> I don't think this will be any > more stable than everyone working in different clones for different > projects. More questions for new/better model: - A clone for a project? Then I would have multiple clones if I work on more than one projects. Actually, I've never only worked on a single proje

[petsc-dev] All petsc-dev users will need to do a reclone of petsc-dev on Tuesday or later

2013-03-11 Thread Barry Smith
On Mar 11, 2013, at 3:12 PM, Hong Zhang wrote: > No matter what new/better model is being introduced, please also try > to make the model > as SIMPLE as possible. > Below is what I learned from Jed this morning (correct me if I'm wrong): > > 1. a stable branch of petsc-dev for users > 2. a dyn

[petsc-dev] Graph of dependencies in include/

2013-03-11 Thread Karl Rupp
tscfix.h, petscconf.h and petscfptimpl.h are included under some >> circumstances - but don't exist. >> >> Best regards, >> Karli >> > -- next part -- A non-text attachment was scrubbed... Name: petsc-include-graph-src.pdf Type: application/pdf Size: 46317 bytes Desc: not available URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20130311/3f9d4187/attachment-0001.pdf>

[petsc-dev] All petsc-dev users will need to do a reclone of petsc-dev on Tuesday or later

2013-03-11 Thread Hong Zhang
No matter what new/better model is being introduced, please also try to make the model as SIMPLE as possible. Below is what I learned from Jed this morning (correct me if I'm wrong): 1. a stable branch of petsc-dev for users 2. a dynamic branch, e.g., named 'next', for group of internal petsc dev

[petsc-dev] possible bug in MatLoad_MPIBAIJ()

2013-03-11 Thread Barry Smith
Hmm, looks like I got the two malloc sizes backwards? locrowlens should be size m and row lengths size mmax? Barry /* distribute row lengths to all processors */ ierr = PetscMalloc((mmax+1)*sizeof(PetscInt),&locrowlens);CHKERRQ(ierr); if (!rank) { mend = m; if (size == 1) m

[petsc-dev] All petsc-dev users will need to do a reclone of petsc-dev on Tuesday or later

2013-03-11 Thread Sean Farley
Karl Rupp writes: > Hi Sean, > > >>> Satish, please remove me from petsc-maint. Also, remove me from the developers webpage. I have already purged petsc-dev from my system and won't be pushing anything else from now on. >>> >>> Huh, why this? This is not forced change of religion... >>

[petsc-dev] All petsc-dev users will need to do a reclone of petsc-dev on Tuesday or later

2013-03-11 Thread Karl Rupp
Hi Sean, >>> Satish, please remove me from petsc-maint. Also, remove me from the >>> developers webpage. I have already purged petsc-dev from my system and >>> won't be pushing anything else from now on. >> >> Huh, why this? This is not forced change of religion... > > Why should I bother? Everyo

[petsc-dev] All petsc-dev users will need to do a reclone of petsc-dev on Tuesday or later

2013-03-11 Thread Sean Farley
Karl Rupp writes: > Hi Sean, > >> Satish, please remove me from petsc-maint. Also, remove me from the >> developers webpage. I have already purged petsc-dev from my system and >> won't be pushing anything else from now on. > > Huh, why this? This is not forced change of religion... Why should I

[petsc-dev] All petsc-dev users will need to do a reclone of petsc-dev on Tuesday or later

2013-03-11 Thread Karl Rupp
Hi Sean, > Satish, please remove me from petsc-maint. Also, remove me from the > developers webpage. I have already purged petsc-dev from my system and > won't be pushing anything else from now on. Huh, why this? This is not forced change of religion... Best regards, Karli

[petsc-dev] All petsc-dev users will need to do a reclone of petsc-dev on Tuesday or later

2013-03-11 Thread Sean Farley
Barry Smith writes: >To users of petsc-dev, > > I promised more details on the planned change and why we are making > them. > > The plan is to move petsc-dev over to the git repository system > (remaining on bitbucket.org so no new accounts are needed) with a simple and > slow

[petsc-dev] All petsc-dev users will need to do a reclone of petsc-dev on Tuesday or later

2013-03-11 Thread Barry Smith
To users of petsc-dev, I promised more details on the planned change and why we are making them. The plan is to move petsc-dev over to the git repository system (remaining on bitbucket.org so no new accounts are needed) with a simple and slow transition from Mecurial and allowi

[petsc-dev] patches for ICC/Cholesky preconditioner on GPUs

2013-03-11 Thread Karl Rupp
Hi Paul, you've got two options: a) Fork the project on Bitbucket, apply the changes to a clone of the forked repository, commit your changes and submit a pull request. Important: This needs to be completed by tomorrow! More detailed information on the process can be found e.g. here: http://

[petsc-dev] patches for ICC/Cholesky preconditioner on GPUs

2013-03-11 Thread Paul Mullowney
;http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20130311/90a52b1b/attachment.html>