Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
G
gluon
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Model registry
Operate
Environments
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Terms and privacy
Keyboard shortcuts
?
Snippets
Groups
Projects
This is an archived project. Repository and other project resources are read-only.
Show more breadcrumbs
ffbs
gluon
Commits
914d8f93
Commit
914d8f93
authored
11 years ago
by
Matthias Schiffer
Browse files
Options
Downloads
Patches
Plain Diff
README: fix code blocks
parent
29e9203c
No related branches found
Branches containing commit
No related tags found
Tags containing commit
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
README.md
+3
-2
3 additions, 2 deletions
README.md
with
3 additions
and
2 deletions
README.md
+
3
−
2
View file @
914d8f93
...
...
@@ -43,11 +43,11 @@ rerun
`
patches
`; the resulting branch will be called `
patched
`, while the commit specified in `
modules
`
can be refered to by the branch `
base
`.
make unpatch
make unpatch
sets the repositories to the `
base
` branch,
make patch
make patch
re-applies the patches by resetting the `
patched
` branch to `
base
` and calling `
git am
`
for the patch files. Calling `
make
` or a similar command after calling `
make unpatch
`
...
...
@@ -56,6 +56,7 @@ is generally not a good idea.
After new patches have been commited on top of the patched branch (or existing commits
since the base commit have been edited or removed), the patch directories can be regenerated
using
make update-patches
If applying a patch fails because you have changed the base commit, the repository will be reset to the old `
patched
` branch
...
...
This diff is collapsed.
Click to expand it.
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