From: Richard Quirk <richard.quirk@gmail.com>
To: <gitster@pobox.com>
Cc: git@vger.kernel.org, Richard Quirk <richard.quirk@gmail.com>
Subject: [PATCH] Documentation gitk: Describe what --merge does
Date: Mon, 28 Apr 2008 22:58:35 +0200 [thread overview]
Message-ID: <1209416315-13925-1-git-send-email-richard.quirk@gmail.com> (raw)
In-Reply-To: <7vlk2zf304.fsf@gitster.siamese.dyndns.org>
Signed-off-by: Richard Quirk <richard.quirk@gmail.com>
---
On Sun, Apr 27, 2008 at 10:37 PM, Junio C Hamano <gitster@pobox.com> wrote:
> Hmm. "the differences" is technically correct in that it shows the
> commits on the diverged histories, but I suspect it would be more
> understandable if we used more explicit wording
Yes, and your explicit wording was much clearer.
I'm not sure if resending this is strictly the Right Thing given that the
words are actually yours. But here's the updated patch so --merge might get
some documentation, just in case.
Documentation/gitk.txt | 6 ++++++
1 files changed, 6 insertions(+), 0 deletions(-)
diff --git a/Documentation/gitk.txt b/Documentation/gitk.txt
index ed3ba83..c40f997 100644
--- a/Documentation/gitk.txt
+++ b/Documentation/gitk.txt
@@ -41,6 +41,12 @@ frequently used options.
Show all branches.
+--merge::
+
+ After an attempt to merge stops with conflicts, show the commits on
+ the history between two branches (i.e. the HEAD and the MERGE_HEAD)
+ that modify the conflicted files.
+
<revs>::
Limit the revisions to show. This can be either a single revision
--
1.5.5.1.91.gb5ae
prev parent reply other threads:[~2008-04-28 20:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-27 15:51 [PATCH] Documentation gitk: Describe what --merge does Richard Quirk
2008-04-27 20:37 ` Junio C Hamano
2008-04-28 20:58 ` Richard Quirk [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=1209416315-13925-1-git-send-email-richard.quirk@gmail.com \
--to=richard.quirk@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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 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).