I want to test the patch with --dry-run, but when it fails, I don't get any rejection files. Is there a way to make a dry run, but save the rejection files so that I can see what went wrong?
--dry-run
patch -o /dev/null(without --dry-run) must send the deleted pieces into oblivion and save the rejection files.
patch -o /dev/null
Source: https://habr.com/ru/post/1758559/More articles:Why is my CGContext bound to borders? - iphonehttps://translate.googleusercontent.com/translate_c?depth=1&pto=aue&rurl=translate.google.com&sl=ru&sp=nmt4&tl=en&u=https://fooobar.com/questions/1758555/generic-repository-select-by-id-in-ef4&usg=ALkJrhgSbiESA1fxRIzqeGQxH3MZEgB4cQPossible boat loads - algorithmWhat is the good practice of using forms in PHP? Can you use OOP PHP in the form? - htmlΠΠ»Π³ΠΎΡΠΈΡΠΌ Π΄Π»Ρ ΠΎΡ Π²Π°ΡΠ° Π½Π°ΡΠ΅Π»Π΅Π½ΠΈΡ ΠΌΠΈΠ½ΠΈΠΌΠ°Π»ΡΠ½ΡΠΌΠΈ ΠΌΠ΅ΡΠΊΠ°ΠΌΠΈ - algorithmΠΡΠ΅Π΄ΠΏΡΠΎΠ΄Π°ΠΆΠ½Π°Ρ ΠΏΠΎΠ΄Π³ΠΎΡΠΎΠ²ΠΊΠ° ΠΊ Π²Π΅Π±-ΠΈΠ³ΡΠ΅ - language-agnosticWP7 Enter an input key to send text from a text field to a text block - c #My extension method is not registered - c #.NET Assemblies: Understanding Type Visibility - reflectionBoolean arrays using "char" - cAll Articles