From: A Large Angry SCM <gitzilla@gmail.com>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Stop making git-merge-recur
Date: Sun, 01 Oct 2006 21:52:58 -0700 [thread overview]
Message-ID: <45209B2A.8070900@gmail.com> (raw)
In-Reply-To: <7vu02nz5w6.fsf@assigned-by-dhcp.cox.net>
Junio C Hamano wrote:
> A Large Angry SCM <gitzilla@gmail.com> writes:
>
>> Git-merge-recur is no longer installed and make clean no longer
>> removes it, so creating making it.
>
> Thanks for noticing.
>
> The bug is actually not installing nor cleaning it. People who
> wanted to stay on the bleeding edge could add "-s recur" on the
> command line, or have "merge.twohead = recur" in the config;
> this is what we actually encouraged people for wider testing.
> We do not suddenly break them. I planned the removal for the
> release after 1.4.3.
>
> This should fix it -- could you eyeball it please?
+1
prev parent reply other threads:[~2006-10-02 4:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-02 2:45 [PATCH] Stop making git-merge-recur A Large Angry SCM
2006-10-02 2:49 ` A Large Angry SCM
2006-10-02 4:41 ` Junio C Hamano
2006-10-02 4:52 ` A Large Angry SCM [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=45209B2A.8070900@gmail.com \
--to=gitzilla@gmail.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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).