aboutsummaryrefslogtreecommitdiff
path: root/docs/install/images/c201/wp-screw.jpg
diff options
context:
space:
mode:
authorAndrew Robbins <contact@andrewrobbins.info>2019-03-27 22:06:38 -0400
committerAndrew Robbins <contact@andrewrobbins.info>2019-03-27 22:22:22 -0400
commit2b351b2fc33cf6e5642fbd1f47984189374fe0e4 (patch)
tree53d1e6b4b58f881b0cf5d84c7adf2d7d4148ed03 /docs/install/images/c201/wp-screw.jpg
parent19752b408d3d819343b9f31f12d17792fe91746c (diff)
downloadlibrebootfr-2b351b2fc33cf6e5642fbd1f47984189374fe0e4.tar.gz
librebootfr-2b351b2fc33cf6e5642fbd1f47984189374fe0e4.zip
libs/git: Fail if patching fails
The recursive call in git_project_patch_recursive() is now performed last so that if a patching attempt fails, the calling functions won't attempt to apply more patches. The consequence of this change is that patches are applied in (nearly) opposite order from before. git_project_prepare_patch() is now called after git_project_prepare_blobs() so that if patching fails and the user chooses to perform additional project actions anyway, such as building, the project is already deblobbed and not a risk to their freedom. I had mistakenly reordered these function calls in a prior commit.
Diffstat (limited to 'docs/install/images/c201/wp-screw.jpg')
0 files changed, 0 insertions, 0 deletions