Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
maestro-core
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Container registry
Model registry
Analyze
Contributor analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
maestro
maestro-core
Commits
e5fa3b19
Commit
e5fa3b19
authored
3 years ago
by
Utz-Uwe Haus
Browse files
Options
Downloads
Patches
Plain Diff
Add remark how to fix weird git subtree pull issues
parent
9d13ca6f
No related branches found
No related tags found
1 merge request
!44
Resolve "Test libfabric update to 1.13 or 1.14"
Pipeline
#84621
failed
3 years ago
Stage: build-and-test
Changes
1
Pipelines
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
INSTALL.md
+9
-0
9 additions, 0 deletions
INSTALL.md
with
9 additions
and
0 deletions
INSTALL.md
+
9
−
0
View file @
e5fa3b19
...
...
@@ -42,6 +42,15 @@ To update a dependency project (e.g. mamba) subtree please do
git subtree pull --prefix=deps/mamba --squash git@gitlab.com:cerl/mamba.git master
```
If
`git`
refuses to do the subtree update insisting 'repo was never added', create a remote for the repo, e.g.,
```
git remote add -f ofiwg git@github.com:ofiwg/libfabric.git
```
and use that repo name for the
`subtree pull`
command.
# Building
...
...
This diff is collapsed.
Click to expand it.
Utz-Uwe Haus
@haus1
mentioned in issue
#96 (closed)
·
3 years ago
mentioned in issue
#96 (closed)
mentioned in issue #96
Toggle commit list
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment