[petsc-dev] still not communicating to google well

[Barry Smith]

On Jun 11, 2012, at 10:59 AM, Jed Brown wrote:

> Perhaps PPPL has some high-traffic pages linking to their version, and we have very few linking to our version. I don't think there is anything we can do about this short of having them take down their page or insert a referral to our copy.

   Can we somehow imbed referral information into what we distribute so that when someone dumps them on a website the referral information gives us credit?

   Barry

> 
> On Mon, Jun 11, 2012 at 8:47 AM, Barry Smith <bsmith at mcs.anl.gov> wrote:
> 
>  How come petscviewerfilesetname to google goes to:
> 
>        • PetscViewerFileSetName
> w3.pppl.gov/m3d/petsc-dev/docs/.../PetscViewerFileSetName.html
> 
> Synopsis. #include "petsc.h" PetscErrorCode PETSC_DLLEXPORTPetscViewerFileSetName(PetscViewer viewer,const char name[]) Collective on PetscViewer ...
>        • #include "src/dm/mesh/meshimpl.h" /*I "petscmesh.h" I*/ #include ...
> w3.pppl.gov/m3d/petsc-dev/src/dm/mesh/mesh.c
> ... ierr = PetscExceptionTry1(PetscViewerFileSetName(viewer, filename), PETSC_ERR_FILE_OPEN); if (PetscExceptionValue(ierr)) { /* this means that a caller...
> 
> 
>        • PetscViewerFileSetName
> www.mcs.anl.gov/petsc/petsc.../docs/.../PetscViewerFileSetName.html
> Synopsis. #include "petscsys.h" PetscErrorCode PetscViewerFileSetName( PetscViewer viewer,const char name[]) Collective on PetscViewer ...
> 
> and MCS is not the first listed?
> 
>   Barry
> 
>