From: Junio C Hamano <junkio@cox.net>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 5/6] Make merge-base a built-in.
Date: Tue, 09 Jan 2007 13:22:53 -0800 [thread overview]
Message-ID: <7vd55nki8i.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <Pine.LNX.4.63.0701091202560.22628@wbgn013.biozentrum.uni-wuerzburg.de> (Johannes Schindelin's message of "Tue, 9 Jan 2007 12:05:42 +0100 (CET)")
Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
> Anyway, I think this series is sane (i.e. I did not find obvious flaws
> reading them).
Heh, there were a few "easter eggs" in the one that are
currently sitting on 'pu', but don't waste your time go hunting
since I've fixed them up in my tree over lunch break.
prev parent reply other threads:[~2007-01-09 21:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-09 10:41 [PATCH 5/6] Make merge-base a built-in Junio C Hamano
2007-01-09 11:05 ` Johannes Schindelin
2007-01-09 21:22 ` 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=7vd55nki8i.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.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