From: Miklos Vajna <vmiklos@frugalware.org>
To: Matthieu Moy <Matthieu.Moy@imag.fr>
Cc: Len Brown <lenb@kernel.org>, git@vger.kernel.org
Subject: Re: octopus limit
Date: Fri, 27 Jun 2008 15:04:35 +0200 [thread overview]
Message-ID: <20080627130435.GM29404@genesis.frugalware.org> (raw)
In-Reply-To: <vpqbq1n5qv2.fsf@bauges.imag.fr>
[-- Attachment #1: Type: text/plain, Size: 296 bytes --]
On Fri, Jun 27, 2008 at 08:33:37AM +0200, Matthieu Moy <Matthieu.Moy@imag.fr> wrote:
> There's a patch around which should remove this limitation (I think
> it's the builtin-ification of merge).
It's in 'pu', so in case you really need it *now*, then just get git.git
and build the 'pu' branch.
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2008-06-27 13:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-27 2:44 octopus limit Len Brown
2008-06-27 6:33 ` Matthieu Moy
2008-06-27 13:04 ` Miklos Vajna [this message]
2008-06-27 12:00 ` Johannes Schindelin
2008-06-27 12:24 ` [PATCH] commit-tree: lift completely arbitrary limit of 16 parents Johannes Schindelin
2008-06-27 13:00 ` Johannes Sixt
2008-06-27 13:02 ` Johannes Schindelin
2008-06-27 17:16 ` Junio C Hamano
2008-06-27 17: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=20080627130435.GM29404@genesis.frugalware.org \
--to=vmiklos@frugalware.org \
--cc=Matthieu.Moy@imag.fr \
--cc=git@vger.kernel.org \
--cc=lenb@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