blt submodule points to an old commit and should follow BLT developments
Open
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 250
- Forks
- 89
- Avg merge
- 34m
- Merged PRs (30d)
- 1
Description
For now SAMRAI subproject 'blt' is set to
```
commit 09173186b693f86e9b5b50ce5f1e61a9c9172ccf (HEAD)
Author: Chris White
Date: Wed Jan 23 10:31:33 2019 -0800
Fix link
```
this is quite old.
Could SAMRAI repo be set to that its blt submodule follows blt newest versions?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Locate SAMRAI's blt submodule entry and compare commit 09173186b693f86e9b5b50ce5f1e61a9c9172ccf with current BLT development. Update the submodule reference to the intended newer BLT commit; done means the repository points to an agreed newer version.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100