git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael J Gruber <git@drmicha.warpmail.net>
To: git@vger.kernel.org
Cc: Junio C Hamano <gitster@pobox.com>
Subject: [PATCH 0/3] git-merge-base -a vs. git-show-branch --merge-base
Date: Wed,  5 Aug 2009 09:59:17 +0200	[thread overview]
Message-ID: <1249459160-3931-1-git-send-email-git@drmicha.warpmail.net> (raw)

The two commands above behave differently when more than two commits are
given. The purpose of this patch series is to correct and improve the
documentation in this regard, and to document the difference in behavior
with a test.

1/3 only depicts the DAG of a test which is already present, to make it
easier for future test writers (such as that of 3/3).

2/3 cleans up the documentation so that man pages and usage strings for
those two commands coincide.

3/3 adds a test case and corrects the documentation with regards to
merge bases for more than two commits.

Michael J Gruber (3):
  t6010-merge-base.sh: Depict the octopus test graph
  git-merge-base/git-show-branch: Cleanup documentation and usage
  git-merge-base/git-show-branch --merge-base: Documentation and test

 Documentation/git-merge-base.txt  |    9 +++++++--
 Documentation/git-show-branch.txt |   13 ++++++++-----
 builtin-merge-base.c              |    2 +-
 builtin-show-branch.c             |    6 +++---
 t/t6010-merge-base.sh             |   18 ++++++++++++++++++
 5 files changed, 37 insertions(+), 11 deletions(-)

             reply	other threads:[~2009-08-05  7:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-05  7:59 Michael J Gruber [this message]
2009-08-05  7:59 ` [PATCH 1/3] t6010-merge-base.sh: Depict the octopus test graph Michael J Gruber
2009-08-05  7:59   ` [PATCH 2/3] git-merge-base/git-show-branch: Cleanup documentation and usage Michael J Gruber
2009-08-05  7:59     ` [PATCH 3/3] git-merge-base/git-show-branch --merge-base: Documentation and test Michael J Gruber

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=1249459160-3931-1-git-send-email-git@drmicha.warpmail.net \
    --to=git@drmicha.warpmail.net \
    --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).