From: Junio C Hamano <gitster@pobox.com>
To: Samuel Bronson <naesten@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] git-cherry.txt: cross reference "git log --cherry"
Date: Sat, 21 Dec 2013 22:58:02 -0800 [thread overview]
Message-ID: <7vk3exjrt1.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <1387484450-935-1-git-send-email-naesten@gmail.com> (Samuel Bronson's message of "Thu, 19 Dec 2013 15:20:50 -0500")
Samuel Bronson <naesten@gmail.com> writes:
> I learned of "git cherry" some days ago, but only learned of --cherry
> and related options to "git log" today[1] (more-or-less by chance).
>
> If the git-cherry(1) manpage had mentioned --cherry, I would have
> learned of these options sooner.
This proposed log message is of an unusual style. It is curious
that somebody learn "cherry" first before "log".
> SEE ALSO
> --------
> -linkgit:git-patch-id[1]
> +linkgit:git-patch-id[1],
> +the `--cherry` option to linkgit:git-log[1]
The description text talks about "changeset (or "diff")", "compares
the changeset rather than the commit id", "diffs are compared",
etc., which is a hint that a lone reference to "patch-id" would be a
page to read about that comparison, which is a good motivation that
may entice the readers to follow that reference.
I am not sure what value the readers of this man page would see to
this addition, though. Unlike the reference to patch-id, it is not
so obvious what gives them motivation to follow this new reference
to "log --cherry". A new sentence in DESCRIPTION section to mention
it (e.g. "'log --cherry' gives similar information") may be needed
at the same time.
prev parent reply other threads:[~2013-12-22 6:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-11 21:39 [PATCH] git-cherry.txt: cross reference "git log --cherry" Samuel Bronson
2013-12-19 20:20 ` Samuel Bronson
2013-12-22 6:58 ` Junio C Hamano [this message]
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=7vk3exjrt1.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=naesten@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.