Document scripted-diffs in developer-notes.md
I sometimes comment on PRs that a scripted-diff would be appropriate, but I don't have any documentation to point to. Fix that.
Document scripted-diffs in developer-notes.md
I sometimes comment on PRs that a scripted-diff would be appropriate, but I don't have any documentation to point to. Fix that.
Typo: indentical (or is that a neologism to mean "identical indentation"?)
Typo: indentical (or is that a neologism to mean "identical indentation"?)
Not a neologism. Just plain old cacography. Now fixed.
548 | @@ -549,6 +549,26 @@ Git and GitHub tips 549 | or `git fetch upstream-pull`. Afterwards, you can use `upstream-pull/NUMBER/head` in arguments to `git show`, 550 | `git checkout` and anywhere a commit id would be acceptable to see the changes from pull request NUMBER. 551 | 552 | +Scripted diffs 553 | +-------------- 554 | + 555 | +For reformating and refactoring commits where the changes can be easily automated using a bash script, we use
typo: reformating -> reformatting
thanks. fixed
Concept ACK
565 | + - `-BEGIN VERIFY SCRIPT-` 566 | + - `-END VERIFY SCRIPT-` 567 | + 568 | +The scripted-diff is verified by the tool `contrib/devtools/commit-script-check.sh` 569 | + 570 | +Commit `bb81e1735575e1c00e808326735168cc9810c174` is an example of a scripted-diff.
Use short version?
ok. changed
LGTM.
ACK 90ab62c4512942f1d252259a892e1cbeeb92789e
utACK 90ab62c
ACK