From: Junio C Hamano <gitster@pobox.com>
To: Christian Couder <chriscool@tuxfamily.org>
Cc: git@vger.kernel.org,
Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Miklos Vajna <vmiklos@frugalware.org>,
Jakub Narebski <jnareb@gmail.com>
Subject: Re: [RFC/PATCH v4 1/2] merge-base: teach "git merge-base" to accept more than 2 arguments
Date: Tue, 29 Jul 2008 23:00:34 -0700 [thread overview]
Message-ID: <7vy73j9ail.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <20080730070414.f7b36eec.chriscool@tuxfamily.org> (Christian Couder's message of "Wed, 30 Jul 2008 07:04:14 +0200")
Thanks; queued. Perhaps I'll add the test scirpt to demonstrate the
topology in the new documentation myself, and the merge-octupos update I
sent earlier to the list can come on top of this series.
prev parent reply other threads:[~2008-07-30 6:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-30 5:04 [RFC/PATCH v4 1/2] merge-base: teach "git merge-base" to accept more than 2 arguments Christian Couder
2008-07-30 6:00 ` 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=7vy73j9ail.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=chriscool@tuxfamily.org \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.com \
--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).