diff options
| author | Teddy Wing | 2020-08-23 20:55:08 +0200 |
|---|---|---|
| committer | Teddy Wing | 2020-08-23 20:55:08 +0200 |
| commit | 623f60844478a3cfc60d697f5e5d804254c01c50 (patch) | |
| tree | 981f8e57bc35fbc3022a58f7442a9e7f92926491 /src/config.rs | |
| parent | bce2e554408404233b66f11e2e342d83c3ca81dd (diff) | |
| download | git-suggestion-623f60844478a3cfc60d697f5e5d804254c01c50.tar.bz2 | |
Rename `git-sugpatch` to `git-sugdiff`
The word "patch" reminds me more of the `patch` Unix command, which is
what `git-sugapply` does.
Since this command outputs diffs, it makes more sense to call it
`sugdiff`. That also brings these closer to the native Git commands,
`git-diff` and `git-apply`.
I had chosen "patch" originally because the command generated a unified
diff that could be used as a patch file to apply to the repo.
Diffstat (limited to 'src/config.rs')
0 files changed, 0 insertions, 0 deletions