diff options
| author | Teemu Hukkanen <tjhukkan@iki.fi> | 2018-09-29 00:29:29 +0200 |
|---|---|---|
| committer | Lars Wirzenius <liw@liw.fi> | 2018-09-29 09:41:01 +0300 |
| commit | d010a026fdbb8ee38145c5e1385547990d427a2d (patch) | |
| tree | b8a5407f96603cea7a04293a32cd508cbde25345 /patches.mdwn | |
| parent | 3e660ff29ee13ba160cd91d253695967621989f5 (diff) | |
| download | ick.liw.fi-d010a026fdbb8ee38145c5e1385547990d427a2d.tar.gz | |
Fix typos
Diffstat (limited to 'patches.mdwn')
| -rw-r--r-- | patches.mdwn | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/patches.mdwn b/patches.mdwn index 54d99be..c69fb56 100644 --- a/patches.mdwn +++ b/patches.mdwn @@ -40,13 +40,13 @@ Here's a few ways you can send us changes: ick-discuss mailing list. (Using "git send-email" is good, too.) If you're sending a patch series consisting of several patches, - add a "cover letter" that expolains what the whole series is about. + add a "cover letter" that explains what the whole series is about. * Make the changes available on a different git server, and send us a URL we can pull from. You can use GitHub or any other server that's convenient for you. You can even create a pull request and send a URL to that. We prefer you send us the URL over e-mail to the - ick-dicusss mailing list, as that gets automatically tracked + ick-discuss mailing list, as that gets automatically tracked # On patches (and pull requests) @@ -55,7 +55,7 @@ We prefer a patch series and pull request to tell a story of the change that is easy to follow and review and understand. * Each patch/commit should have a clear commit message. The commit - message should explain why the change is made, and not just repharse + message should explain why the change is made, and not just rephrase the diff. The commit message should stand on its own, as it will be read on its own in the future, when someone is debugging the program, possibly with "git bisect". |