From: Jeff King <peff@peff.net>
To: Junio C Hamano <junkio@cox.net>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>,
"Shawn O. Pearce" <spearce@spearce.org>,
git@vger.kernel.org
Subject: Re: [RFC/PATCH] commit-tree: bump MAX_PARENTS to 128
Date: Tue, 27 Feb 2007 03:19:33 -0500 [thread overview]
Message-ID: <20070227081933.GA13021@coredump.intra.peff.net> (raw)
In-Reply-To: <7vr6scj9qt.fsf@assigned-by-dhcp.cox.net>
On Tue, Feb 27, 2007 at 12:16:42AM -0800, Junio C Hamano wrote:
> But as Shawn pointed out, Octopus makes bisect less (much less)
> efficient for the end users, I tend to think the current 16 is
> already insanely large.
Did you look at my "why I need a huge octopus" description? Is there a
better way to do it? Should I simply do a bunch of pair-wise merges?
I'll almost certainly never bisect it, but the octopus "looks right" in
gitk (though I have to admit, it's really not _that_ big a deal -- it's
almost more readable to look at pairwise merges anyway).
-Peff
next prev parent reply other threads:[~2007-02-27 8:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-26 12:15 [RFC/PATCH] commit-tree: bump MAX_PARENTS to 128 Jeff King
2007-02-26 14:31 ` Shawn O. Pearce
2007-02-26 16:38 ` Johannes Schindelin
2007-02-27 8:16 ` Junio C Hamano
2007-02-27 8:19 ` Jeff King [this message]
2007-02-27 10:23 ` Junio C Hamano
2007-02-27 10:52 ` Jeff King
2007-02-27 11:06 ` Junio C Hamano
2007-02-27 11:31 ` Andy Parkins
2007-02-27 11:39 ` Jeff King
2007-02-27 14:04 ` Jakub Narebski
2007-02-27 15:46 ` Johannes Schindelin
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=20070227081933.GA13021@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=spearce@spearce.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).