Skip to content
Snippets Groups Projects
Unverified Commit 3ac9d34c authored by Matthias Schiffer's avatar Matthias Schiffer
Browse files

docs: dev/basics: remove outdated docs about patch and unpatch commands

parent ce53ed20
No related branches found
No related tags found
No related merge requests found
Hide whitespace changes
Inline Side-by-side
Showing
with 1 addition and 15 deletions
docs/dev/basics.rst
+ 1
− 15
View file @ 3ac9d34c
...@@ -34,21 +34,7 @@ rerun ...@@ -34,21 +34,7 @@ rerun
`patches`; the resulting branch will be called `patched`, while the commit specified in `modules` `patches`; the resulting branch will be called `patched`, while the commit specified in `modules`
can be refered to by the branch `base`. can be refered to by the branch `base`.
:: After new patches have been commited on top of the `patched` branch (or existing commits
make unpatch
sets the repositories to the `base` branch,
::
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`
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 since the base commit have been edited or removed), the patch directories can be regenerated
using using
......
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment

Impressum - Datenschutz