| /petsc/share/petsc/ |
| H A D | chkerrconvert.py | 89 new_lines,changes = [],[]
104 changes.append((lineno,last[0],None))
128 changes.append((lineno,line,repl))
132 … self.delete_unused_error_code_decls(error_code_decls,error_code_uses,new_lines,delete_set,changes)
137 changes.append((len(new_lines),new_lines[-1],None))
145 return new_lines,changes,delete_set
148 …delete_unused_error_code_decls(self,error_code_decls,error_code_uses,new_lines,delete_set,changes): argument
178 for i,(cln,_,_) in enumerate(changes):
180 changes.insert(i,change)
184 changes.append(change)
[all …]
|
| /petsc/doc/developers/contributing/ |
| H A D | developingmr.md | 69 - For any new features or API changes you introduced add information on them to `doc/changes/dev.rs…
71 - Inspect changes and stage code using standard Git commands, e.g.
118 - Include {doc}`tests </developers/testing>` which cover any changes to the source code.
142 Often a branch's commit history does not present a logical series of changes.
143 … bug-fixes or tiny improvements may accumulate. One commit may contain multiple orthogonal changes.
144 The order of changes may be incorrect. Branches without a clean commit history will often break `gi…
145 …ass the PETSc CI testing, while presenting a small-as-possible set of very closely related changes.
164 … branch is not compatible with the remote copy of the branch. You must force push your changes with
171 otherwise you will lose those changes. Never do a `git pull` immediately after you rebase since tha…
173 You can use `git log` to see the recent changes to your branch and help determine what commits shou…
[all …]
|
| H A D | pipelines.md | 123 new changes to the branch you have pushed since that pipeline was started - it retries the
|
| /petsc/lib/petsc/bin/maint/abi-compliance-checker/ |
| H A D | README.md | 17 …s changes in API/ABI (ABI=API+compiler ABI) that may break binary compatibility and/or source comp…
|
| /petsc/doc/changes/ |
| H A D | index.md | 4 upcoming releases; **small changes in usage and calling sequences of
14 release proceed through the changes listed in this file in increasing
17 include/petscversion.h) Many of the interface changes can be handled
|
| H A D | 232.md | 11 - Added C99 complex support. [check configure changes below]
|
| H A D | 317.md | 26 …C_VERSION_PATCH` so as to not have confusion with patch releases where the subminor version changes
74 …pt is considered "beta" software. It was used to facilitate the `CHKERR` changes during developmen…
250 …daptation interface to Mmg and 3D mesh adaptation interface to ParMmg. Mmg/ParMmg specific changes:
|
| /petsc/doc/community/ |
| H A D | governance.md | 36 and best efforts (e.g., all substantive API changes must be posted to the mailing list in order to …
48 - Vote on changes to the NumFOCUS signatories which will be conducted by the council using the Schu…
53 - Vote on {any}`changes to the governance policy<governance_changes>` (this document) with a 2/3 ma…
92 …petsc> on this file (`doc/community/governance.rst`) constitute proposed changes to the governance…
93 After a community discussion of the proposed changes, the PETSc Council can pass changes to the doc…
|
| H A D | mailing.md | 20 - Recommend changes or additions to the development team.
|
| /petsc/src/sys/tests/options/output/ |
| H A D | ex55_6b.out | 2 See https://petsc.org/release/changes for recent updates.
|
| H A D | ex55_5b.out | 2 See https://petsc.org/release/changes for recent updates.
|
| H A D | ex55_6c.out | 2 See https://petsc.org/release/changes for recent updates.
|
| H A D | ex55_5c.out | 2 See https://petsc.org/release/changes for recent updates.
|
| H A D | ex55_5a.out | 2 See https://petsc.org/release/changes for recent updates.
|
| H A D | ex55_6a.out | 2 See https://petsc.org/release/changes for recent updates.
|
| /petsc/doc/developers/ |
| H A D | mrfork.md | 5 `Developers` at times, need to checkout and build changes from a merge request fork branch. Any one…
38 # Commit and push changes to a merge request fork branch
|
| /petsc/doc/manual/ |
| H A D | versionchecking.md | 30 Though we try to avoid making changes to the PETSc API, they are inevitable; thus we
31 provide tools to help manage one's application to be robust to such changes.
|
| H A D | about_this_manual.md | 40 Since PETSc is under continued development, small changes in usage and
|
| /petsc/doc/overview/ |
| H A D | index.md | 25 ../changes/index
|
| H A D | gpu_roadmap.md | 14 **runtime** options and configuration options with no changes to the API.
|
| /petsc/doc/manualpages/ |
| H A D | index.md | 30 ../changes/index.rst
|
| /petsc/src/sys/yaml/ |
| H A D | README.md | 22 of code. This will make it quite easy to merge back upstream changes
|
| /petsc/doc/install/ |
| H A D | download.md | 109 - MINOR version, with new functionality and likely small API changes; most changes are backward com…
|
| /petsc/src/binding/petsc4py/ |
| H A D | CHANGES.rst | 73 - Fix build issues after changes in recent PETSc patch releases.
259 - Update for API cleanups, changes, and new calls in PETSc 3.1 and
|
| /petsc/ |
| H A D | gmakefile | 174 # ABI changes like new or removed symbols requires relinking the dependent libraries. ABI should
266 # all sources should get recompiled when petscvariables changes (i.e when configure is rerun or whe…
|