aboutsummaryrefslogtreecommitdiffstats
path: root/git.sr.ht/send-email.md
diff options
context:
space:
mode:
authorDrew DeVault <sir@cmpwn.com>2018-09-30 10:03:50 -0400
committerDrew DeVault <sir@cmpwn.com>2018-09-30 10:03:50 -0400
commit634cacc389541e7410fbdcfe938118d1049c94ab (patch)
treebf70fd8544a0d88fac101e99ae9ceb27ae8da8cf /git.sr.ht/send-email.md
parent2788c4c01f433928bfdaddb9a03b8591573050c8 (diff)
downloadsr.ht-docs-634cacc389541e7410fbdcfe938118d1049c94ab.tar.gz
Further clarifications and corrections to rev spec
Diffstat (limited to 'git.sr.ht/send-email.md')
-rw-r--r--git.sr.ht/send-email.md8
1 files changed, 5 insertions, 3 deletions
diff --git a/git.sr.ht/send-email.md b/git.sr.ht/send-email.md
index 5b6bb21..cd6c144 100644
--- a/git.sr.ht/send-email.md
+++ b/git.sr.ht/send-email.md
@@ -89,8 +89,10 @@ local keyring; consult [`git credential`][git-credential] for details.
## Send the patches along
When you've configured `git send-email`, completed your work, and you're ready
-to send your patches in, you can run `git send-email --annotate [rev-list...]`.
-The `rev-list` is the same as any other [revision specification][rev-spec]. If
+to send your patches in, you can run `git send-email --annotate [rev-spec...]`.
+The `rev-spec` is the same as any other [revision specification][rev-spec], and
+send-email will prepare patches from that commit to the tip (unless you specify
+`-1`, `-2`, etc, in which case it will prepare up to that many patches). If
you're in a hurry, here are a few quick examples:
- `HEAD^` just includes the last commit
@@ -98,7 +100,7 @@ you're in a hurry, here are a few quick examples:
- `origin/master` includes all commits since diverging from `origin/master`
- `0fdbc0da` only includes commit `0fdbc0da` when specified with `-1`
- `0fdbc0da` includes commit `0fdbc0da` and the 2 commits prior when specified
- with `-2`
+ with `-3`
[rev-spec]: https://www.git-scm.com/docs/gitrevisions