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/bin/git-sugdiff.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/bin/git-sugdiff.rs')
| -rw-r--r-- | src/bin/git-sugdiff.rs | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/src/bin/git-sugdiff.rs b/src/bin/git-sugdiff.rs index 3bc787a..c703e2b 100644 --- a/src/bin/git-sugdiff.rs +++ b/src/bin/git-sugdiff.rs @@ -29,7 +29,7 @@ fn main() { let config = match Config::get( &args, - "usage: git sugpatch [options] <suggestion>...", + "usage: git sugdiff [options] <suggestion>...", ) { Ok(c) => c, Err(e) => { |