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 /doc/git-sugapply.1.txt | |
| 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 'doc/git-sugapply.1.txt')
| -rw-r--r-- | doc/git-sugapply.1.txt | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/git-sugapply.1.txt b/doc/git-sugapply.1.txt index d513505..ca55726 100644 --- a/doc/git-sugapply.1.txt +++ b/doc/git-sugapply.1.txt @@ -68,4 +68,4 @@ They can also be mixed: SEE ALSO -------- -git-sugpatch(1) +git-sugdiff(1) |