From: Junio C Hamano <gitster@pobox.com>
To: Christian Couder <chriscool@tuxfamily.org>
Cc: git@vger.kernel.org, Miklos Vajna <vmiklos@frugalware.org>
Subject: Re: [RFC/PATCH] merge-base: teach "git merge-base" to accept more than 2 arguments
Date: Fri, 25 Jul 2008 21:37:08 -0700 [thread overview]
Message-ID: <7vzlo5mfbf.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <20080726055920.3a2fc8e7.chriscool@tuxfamily.org> (Christian Couder's message of "Sat, 26 Jul 2008 05:59:20 +0200")
Christian Couder <chriscool@tuxfamily.org> writes:
> Before this patch "git merge-base" accepted only 2 arguments, so
> only merge bases between 2 references could be computed.
>
> The purpose of this patch is to make "git merge-base" accept more
> than 2 arguments so that the merge bases between the first given
> reference and all the other references can be computed.
I think this is a logical conclusion of merge_bases_many(). You need
tests and docs, though.
prev parent reply other threads:[~2008-07-26 4:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-26 3:59 [RFC/PATCH] merge-base: teach "git merge-base" to accept more than 2 arguments Christian Couder
2008-07-26 4:25 ` Johannes Schindelin
2008-07-26 4:37 ` 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=7vzlo5mfbf.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=chriscool@tuxfamily.org \
--cc=git@vger.kernel.org \
--cc=vmiklos@frugalware.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).