From: Eric Wong <normalperson@yhbt.net>
To: Junio C Hamano <gitster@pobox.com>, Andrew Myrick <amyrick@apple.com>
Cc: git@vger.kernel.org, sam@vilain.net
Subject: Re: [PATCH] git-svn: Remove obsolete MAXPARENT check
Date: Mon, 21 Dec 2009 14:39:18 -0800 [thread overview]
Message-ID: <20091221223918.GA22872@dcvr.yhbt.net> (raw)
In-Reply-To: <1261434174-298-1-git-send-email-amyrick@apple.com>
Andrew Myrick <amyrick@apple.com> wrote:
> Change git-svn not to impose a limit of 16 parents on a merge.
>
> This limit in git-svn artificially prevents cloning svn repositories
> that contain commits with more than 16 merge parents.
>
> The limit was removed from builtin-commit-tree.c for git v1.6.0 in commit
> ef98c5cafb3e799b1568bb843fcd45920dc62f16, so there is no need to check for it
> it in git-svn.
>
> Signed-off-by: Andrew Myrick <amyrick@apple.com>
Thanks Andrew,
Acked-by: Eric Wong <normalperson@yhbt.net>
and pushed out to git://git.bogomips.org/git-svn along with the
rest of the stuff already pushed out last night.
Andrew Myrick (1):
git-svn: Remove obsolete MAXPARENT check
Eric Wong (2):
git svn: fix --revision when fetching deleted paths
update release notes for git svn in 1.6.6
Sam Vilain (5):
git-svn: expand the svn mergeinfo test suite, highlighting some failures
git-svn: memoize conversion of SVN merge ticket info to git commit ranges
git-svn: fix some mistakes with interpreting SVN mergeinfo commit ranges
git-svn: exclude already merged tips using one rev-list call
git-svn: detect cherry-picks correctly.
--
Eric Wong
prev parent reply other threads:[~2009-12-21 22:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-21 22:22 [PATCH] git-svn: Remove obsolete MAXPARENT check Andrew Myrick
2009-12-21 22:39 ` Eric Wong [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=20091221223918.GA22872@dcvr.yhbt.net \
--to=normalperson@yhbt.net \
--cc=amyrick@apple.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=sam@vilain.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