From: Samuel Bronson <naesten@gmail.com>
To: git@vger.kernel.org
Subject: [PATCH] git-cherry.txt: cross reference "git log --cherry"
Date: Thu, 11 Apr 2013 17:39:39 -0400 [thread overview]
Message-ID: <5167369f.ea15340a.5e12.0282@mx.google.com> (raw)
I learned of "git cherry" some days ago, but only learned of --cherry
and related options to "git log" today (more-or-less by chance).
If the git-cherry(1) manpage had mentioned --cherry, I would have
learned of these options sooner.
Signed-off-by: Samuel Bronson <naesten@gmail.com>
---
Documentation/git-cherry.txt | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/Documentation/git-cherry.txt b/Documentation/git-cherry.txt
index f6c19c7..076fe68 100644
--- a/Documentation/git-cherry.txt
+++ b/Documentation/git-cherry.txt
@@ -62,7 +62,8 @@ OPTIONS
SEE ALSO
--------
-linkgit:git-patch-id[1]
+linkgit:git-patch-id[1],
+the `--cherry` option to linkgit:git-log[1]
GIT
---
--
1.8.2.1
next reply other threads:[~2013-04-11 22:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-11 21:39 Samuel Bronson [this message]
2013-12-19 20:20 ` [PATCH] git-cherry.txt: cross reference "git log --cherry" Samuel Bronson
2013-12-22 6:58 ` Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5167369f.ea15340a.5e12.0282@mx.google.com \
--to=naesten@gmail.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).